I have some common knowledge / libraries that I am referring to from my main application. Each module / library can be configured and after creating them, each has a configuration file like MyModule1.dll.config, MyModule2.dll.config.
When I create an app for my main application, the config file is output to the output directory.
I'm thinking of configuring MyModule1, MyModule2, etc. Should I include the config section for each in the app.config file or do I have a separate config file module for each where I load a config file for each one? Separate configuration of the module is described here:? This would mean that I will also copy MyModule1.dll.config and MyModule2.dll.config to the output output directory.
Edit:
Edit:
With my Module1.dll I can explicitly load MyModule1.dll.config
Uri P = new Uri (System. Reflections.exceptions; Gate Accelerating Assemblade (. Codebase); Configuration Config = Configuration Manager OpenXE configuration (P. lockpath);
But if MyModule1.dll refers to and uses My Normal Library MyCommonLib.dll, then how to configure MyCommonLib.dll to configure the same config file from MyModule1.dll.config Could?
If you are using the Properties folder system in Visual Studio, and Visual Studio will automatically convert them to To sync with, you want to use a config-per-module approach that you just described for productivity.
Alternatively, if you are working with only or with entries, then it may be easier than a configuration file. My only advice here is the easiest and most natural way for everyone working on the project.
Comments
Post a Comment