application.exe.config file vanishes on compilation

  • Thread starter Thread starter Jay Ayliff
  • Start date Start date
J

Jay Ayliff

If you put configuration settings in a text file in the \bin folder, named
the same as the exe, but with .config (e.g. config file for myapp.exe will
be myapp.exe.config), then the config file is deleted when you build the
exe. If you set the file to readonly then it doesn't get deleted, but of
course then you can't change it from your program! This 'feature' came in
with Visual Studio 2003. In the original VS.NET the config file did not get
deleted.

Has anyone else noticed this, and is there a better way of storing
configuration settings?

Regards

Jay Ayliff
Stalis Ltd
 
* "Jay Ayliff said:
If you put configuration settings in a text file in the \bin folder, named
the same as the exe, but with .config (e.g. config file for myapp.exe will
be myapp.exe.config), then the config file is deleted when you build the
exe. If you set the file to readonly then it doesn't get deleted, but of
course then you can't change it from your program! This 'feature' came in
with Visual Studio 2003. In the original VS.NET the config file did not get
deleted.
Click to expand...

Copy the file (named "App.config") to your project's source directory,
add it to the project and select an appropriate build action. The file
will be copied to the "bin" directory automatically when compiling.
 
Ah, I should have thought of that myself. I suppose you also need to copy it
back to the source directory from bin if your app changes it?

Jay
 
* "Jay Ayliff said:
Ah, I should have thought of that myself. I suppose you also need to copy it
back to the source directory from bin if your app changes it?
Click to expand...

Yes. This new "feature" fixes a bug in VS.NET 2002.
 
Back
Top