Your mail is a bit confusing....
Anyway 1st you should know that 1.1 is a debuged version of 1.0, so it's
safer to use 1.1
Furthermore I'm not quite sure you could compile against 1.1 and run with
1.0
Also "debuging" a config file has no meaningfull meaning. You don't "debug"
a config file as no there is no code in a config file.
If you want to be sure to run on 1.0, why not set your app as supporting
only 1.0 while testing, like that:
> <configuration>
> <startup>
> <supportedRuntime version="v1.0.3705" />
> </startup>
> </configuration>
?
>I posted this originally in
>microsoft.public.dotnet.framework.windowsforms -- but this is probably a
[quoted text clipped - 17 lines]
> Is there a way to debug a config file? Where should I look to make
> progress?
Alexandra Stanns - 02 Sep 2005 14:41 GMT
Sorry if my mail was confusing.... I may also have messed up a bit with
version numbers :-(
Basically, I develop my app on VS 2003 - v1.1.4322 - and want it to also
run on v1.3.0.705
Therefore I created a config file -- but my app does not load on v1.3.0.705
(it looks for mscorwks.dll in v.1.1.4322)
So my question is -- how do I make progress here? How can I find what is
wrong (the config file, the installation, ....)?
Thanks a lot,
Alexandra.
> Your mail is a bit confusing....
>
[quoted text clipped - 37 lines]
>> Is there a way to debug a config file? Where should I look to make
>> progress?
Norman Yuan - 02 Sep 2005 15:23 GMT
In VS2003's Solution explorer, right-click the app project->Properties. Then
in "Common Properties->General->Supported Runtime", click "..." button, it
gives you 3 options for the .NET runtime version.
> Sorry if my mail was confusing.... I may also have messed up a bit with
> version numbers :-(
[quoted text clipped - 51 lines]
>>> Is there a way to debug a config file? Where should I look to make
>>> progress?
Alexandra Stanns - 03 Sep 2005 03:43 GMT
Thanks a lot -- now it works.
The setting actually creates a config file with the same <startup> section
as the one I wrote, however it also adds a bunch of element under the
<runtime> section -- and that does the trick.
> In VS2003's Solution explorer, right-click the app project->Properties.
> Then in "Common Properties->General->Supported Runtime", click "..."
[quoted text clipped - 55 lines]
>>>> Is there a way to debug a config file? Where should I look to make
>>>> progress?