I'm working on merging 21 projects into 1 Visual Studio solution, to have some projects be jointly shared (or be depend on). All of those projects are made up of WinFrm app, WinSrvc app, Class app (dll) and Websites.
I did some Google surfings about whether should I implement Config Reader to read the *.dll.config file then I learned that it is not worth it, due to issues and problems, and that I should create a custom xml file for the DLL's built-in scripts to read it from. Or add "AppSetting" tags to all of the web's web.config and exe's config's files, then pass on the value as needed parameters to some DLL files.
I do not what to add many "AppSetting" tags to all of the web's web.config or exe's config files so I resigned in defeated to do custom xml file instead. The challenge I have is different directory path during production or Visual-Studio debugging.
The question is why does Visual Studio or .NET allows creation of *.dll.config in the 1st place? Everyone says *.dll.config is a no no!!! Help me to understand this which Microsoft just did.
Many Thanks...