DotSpy,
> - why are there TWO config files, myapp.exe.config and
> app.config ?
This is normal.
Microsoft fixed a 'feature' of VS.NET 2002 in VS.NET 2003. :-|
You need to add your config file to your VS.NET project's root folder as
app.config, it needs to be named "app.config" without the quotes. When you
build your project VS.NET (both 2002 & 2003) will copy the app.config file
from the project root to your output folder and name it appropriately
(myproject.exe.config).
> - is it wise to keep only app.config ?
With VS.NET 2003 it is the only option, VS.NET 2002 had the 'bug' that was
fixed. Hopefully VS.NET 2004 keeps the VS.NET 2003 behavior as it seems the
most correct...
> - why is this config file overwritten by dynamic
> parameters ?
Which one is overwritten, the one in the bin folder. The folder that has all
the outputs from the build? Remember the config file is an output from the
build also, so it gets replaced with the app.config that is part of your
project. Also the app.config will be named correctly, so if you change
project properties the config created in the bin folder will be correct.
Hope this helps
Jay
> I did build a small VB Net application with a
> configuration file called myapp.exe.config and it worked
[quoted text clipped - 15 lines]
> - why is this config file overwritten by dynamic
> parameters ?