Bragadiru,
The .Net framework, by default does not use a my.dll.config. Any dll in your
solution will use the mine.exe.config file.
You can 'force' your DLL to use the my.dll.config, by creating a new
AppDomain, setting the AppDomainSetup.ConfigurationFile to 'my.dll.config',
then run the dll in the second AppDomain. Then ensure that the dll runs in
this second AppDomain, while your exe runs in the first AppDomain... There
have been posts in one of the microsoft public dotnet newsgroups on how to
get it to work, I do not have links handy.
Currently I manually add the settings the DLL needs to my 'mine.exe.config'
file and let the dll use those. I use custom configuration sections to
ensure that DLL settings are isolated from exe settings.
These dll configuration sections are defined via:
http://msdn.microsoft.com/library/de...onhandlers.asp
and:
http://msdn.microsoft.com/library/de...ionsschema.asp
Eventually I intend on creating a custom
System.Configuration.Install.Installer class that will add the needed
entries to the app.config that the dll needs.
Hope this helps
Jay
"Bragadiru" <ad****@cims.ro> wrote in message
news:OZ**************@tk2msftngp13.phx.gbl...
I have a solution with 2 projects: a class library(my.dll) + a windows
application (mine.exe). In exe project I have a reference to the dll. In
both I have app.config files, BUT only mine.exe.config file is generated
in \bin\Debug\ folder of exe app. What can I do to generate my.dll.config
from app.config, too?
Thnx for any advice.