Sep 20, 2006 - 08:20 AM
If you tell the "users" of the dll to place the configuration settings in the app.config or the web.config, don´t you always have access to the configuration settings without having to know where they are located physically?
Sep 20, 2006 - 07:15 PM
Yes, this is true for the
The web.config and the app.config are in some parts different. This is something I always wonder about, Why doesn't Microsoft put everyting on one common level. Interchangeability seems to be the big buzz word in most of their areas but then you get different structures of configuration files etc. This is my problem. For web pages you are supposed to have your connectionStrings in the connectionStrings section, for windows apps they are in the appSettings section etc.
And why not having a MyDll.app.config file which could be deployed with teh library. Sorry, I start whinging and whining here!
Sep 21, 2006 - 11:59 AM
And yes, I agree with you on the criticism of the configuration files not being structured equally.
Let me know, how you solve this in the end.
Feb 19, 2007 - 02:06 PM
sorry that I was a bit quiet inthe last couple of weeks.
I solved the problem exactly as you described it above. I bit the bullet and avoided to use the connectionString section. I created my own key/value pairs.