App.Config versus exe.config

  • Thread starter Thread starter Chris Zopers
  • Start date Start date
C

Chris Zopers

Hello,

I've developed a dll that uses an App.config file to read some settings.

After that, I've developed two executables and both use the dll I just
mentioned.

After building the exe's, both exe's get an exe.config file in the bin
directory and this is the same file as the App.config file of the dll.

I do not want this. I just want one configuration file that is used by
the dll, now I get for both executables a separate config file and this
is done automatically when I build the exe projects. So now the same
settings are in two different config files.

Does anyone know how I can solve this?

Greetings,
Chris.
 
Chris Zopers said:
Hello,

I've developed a dll that uses an App.config file to read some settings.

After that, I've developed two executables and both use the dll I just
mentioned.

After building the exe's, both exe's get an exe.config file in the bin
directory and this is the same file as the App.config file of the dll.

I do not want this. I just want one configuration file that is used by
the dll, now I get for both executables a separate config file and this
is done automatically when I build the exe projects. So now the same
settings are in two different config files.
Click to expand...
Does anyone know how I can solve this?
Click to expand...

You do know there is the ConfigurationManager in .Net 2.0 and the
Applications Block in .Net 1.1 using the ConfigurationSettings, which both
of them do the same thing in working App.config or the appname.execonfig.

http://www.dotnetfun.com/articles/framework/2.0/WhatsNew20ConfigurationManager.aspx
 
DLL dont read app.config file. You have to read configuration data and
send it to dll.
 
Back
Top