I recently moved a large project (Managed C++ and C#)
using extensive app.exe.config trace switches for
debugging from VS.NET 2002 to VS.NET 2003. Now whenever I
build (or even the implicit build caused by Debug /
Start) to deletes the app.exe.config file!
This would make debugging unusable, since all my tracing
is conditionalized. I've been able to workaround by using
a Post-Build action to copy app.exe.config.real to
app.exe.config, but this is awkward, fragile, and
potentially confusing.
Is this just me, a known problem, or a "feature"? Any
help is greatly appreciated.
Seth
----
Seth Porter
Software Engineer
EyeSee360, Inc.
<symmetry@eyesee360.com
Jason Wilden - 31 Jul 2003 20:49 GMT
Seth,
This, I believe, has come up in a number of postings and is a new feature
of VS.NET 2003.
AFAIK you now need to add the app.config file to the solution source-tree as
a project file, it will then be automatically copied into the build output
directory each time you compile the application. Any existing appconfig
file found in the output folder is overwritten.
You should also be aware that even if you don't have an app.config file in
the solution, any existing app.config file found in the build output
directories will always still be deleted.
Hope this helps
Jason.
> I recently moved a large project (Managed C++ and C#)
> using extensive app.exe.config trace switches for
[quoted text clipped - 18 lines]
> EyeSee360, Inc.
> <symmetry@eyesee360.com