If I have a web application (with its own web.config) and a .dll it uses happens to have its own app.config which settings file wins when there is a conflict?
views:
161answers:
2
+2
A:
No, you will not have any conflict because a .dll cannot have its own .config file.
Even if you put a .config file for your library in the same folder, the application is simply not going to pick up the values from it.
If you wish to use some of those values, you can merge them into your web.config.
Mark Seemann
2009-09-21 10:49:17
The situation I'm looking at infront of me begs to differ...
Kirschstein
2009-09-21 10:50:17
@Kirschtein: Which is?
Mark Seemann
2009-09-21 10:51:21
There's an app.config file inside this library, with connection strings mentioned.
Kirschstein
2009-09-21 10:53:29
@Kirschtein: They will not be picked up by the application by default. Is your scenario an add-in scenario. If so, the application may load the library into a separate AppDomain and point that AppDomain to the app.config in question, but otherwise those connection strings will not be loaded by the library unless they are specified in your web.config.
Mark Seemann
2009-09-21 11:00:49
A:
You can merge settings from another configuration file into your web.config file. This also allows you to override values aswell if they have the same key.
web.config
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings file="YourSettings.config">
<add key="KeyToOverride" value="Original" />
<add key="KeyToNotOverride" value="Standard" />
</appSettings>
...
YourSettings.config
<appSettings>
<add key="KeyToOverride" value="Overridden" />
<add key="KeyToBeAdded" value="EntirelyNew" />
</appSettings>
James
2009-09-21 10:53:41