Reputation: 21
I've got an assembly, e.g. "DoCommonStuffAssembly", with its own app.config.
This assembly is referenced by two different assemblies, e.g. "BusinessLogic01" and "BusinessLogic02", with their own version of the configuration section of DoCommonStuffAssembly.
Now I need both BusinessLogic01 and BusinessLogic02 to be referenced in the same ASP.NET application, but both should have different versions of the configuration section of DoCommonStuffAssembly (like log folder or something like that).
How can I do this? Where do I have to make changes to make DoCommonStuffAssembly useful in an environment like this?
Upvotes: 0
Views: 105
Reputation: 161773
You cannot handle this scenario, unless the two BusinessLogic assemblies are referenced in different virtual paths. You can have a web.config in each path. If the two BusinessLogic assemblies were only referenced in different paths, then you could have one web.config with each set of settings.
At least, I think this would work.
Upvotes: 1