DLL.Config
-
If I have an assembly, eg Foo.Dll And then create a config for it , eg Foo.Dll.Config What are the requirements for the config file to be uses? Is it possible to load such config (standard .NET config) for a dynamically loaded assembly? or can I somehow force a specific config to be loaded so it can be accessed from the Settings class? The problem I'm facing is a 3rd party tool that loads assemblies from a specific folder. And I want to supply a standard .NET config for those assemblies. Right now, those configs are apparently ignored and the settings will fall back to the hardcoded values in the settings class that VS.NET generates..
-
If I have an assembly, eg Foo.Dll And then create a config for it , eg Foo.Dll.Config What are the requirements for the config file to be uses? Is it possible to load such config (standard .NET config) for a dynamically loaded assembly? or can I somehow force a specific config to be loaded so it can be accessed from the Settings class? The problem I'm facing is a 3rd party tool that loads assemblies from a specific folder. And I want to supply a standard .NET config for those assemblies. Right now, those configs are apparently ignored and the settings will fall back to the hardcoded values in the settings class that VS.NET generates..
Deja View - the feeling that you've seen this post before.