Why dll assembly read AppSetting from its executable Config file

[keith]

In my app, an executable (app.exe) calls functions from an assembly dll
(subapp.dll).

app.exe has config file: app.exe.config
<?xml version="1.0" encoding="utf-8" ?>
<configuratio n>
<appSettings>
<add key="configVal" value="exe config" />
</appSettings>
</configuration>

and subapp.dll.conf ig has config file: subapp.dll.conf ig
<?xml version="1.0" encoding="utf-8" ?>
<configuratio n>
<appSettings>
<add key="configVal" value="dll config" />
</appSettings>
</configuration>

When ran the app, the dll got setting from the exe's config file
instead of its own config file.

Can you tell why and how to fix it?

Thanks

[Scott Allen]

Hi keith:

The config files are assigned per application domain, so this is the
expected behavior.

Mike Woodring has a sample that uses per-assembly config files:
http://www.bearcanyon.com/dotnet/#AssemblySettings

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 5 Nov 2004 10:38:02 -0800, "keith"
<ke***@discussi ons.microsoft.c om> wrote:

In my app, an executable (app.exe) calls functions from an assembly dll
(subapp.dll) .

app.exe has config file: app.exe.config
<?xml version="1.0" encoding="utf-8" ?>
<configuration >
<appSettings>
<add key="configVal" value="exe config" />
</appSettings>
</configuration>

and subapp.dll.conf ig has config file: subapp.dll.conf ig
<?xml version="1.0" encoding="utf-8" ?>
<configuration >
<appSettings>
<add key="configVal" value="dll config" />
</appSettings>
</configuration>

When ran the app, the dll got setting from the exe's config file
instead of its own config file.

Can you tell why and how to fix it?

Thanks

[Marc Scheuner [MVP ADSI]]

>In my app, an executable (app.exe) calls functions from an assembly dll

(subapp.dll) .
app.exe has config file: app.exe.config
and subapp.dll.conf ig has config file: subapp.dll.conf ig
When ran the app, the dll got setting from the exe's config file
instead of its own config file.
Can you tell why and how to fix it?

Why? Because that's the way it was designed to work!

You can only "fix" it by supplying your own logic to parse and
interpret the sub-assembly's .config file - no native .NET classes or
support for that in the system, sorry.

Marc
=============== =============== =============== =============== ====
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)i nova.ch