Solution
- From: James Crosswell <james@xxxxxxxxxxxxxx>
- Date: Sat, 09 Dec 2006 21:13:26 +0100
So I finally found some decent documentation on this:
https://secure.codeproject.com/dotnet/mysteriesofconfiguration.asp
To be honest, what I was hoping would be a couple of lines of code appears to require writing literally pages and pages of code to define classes and then some fiddling around writing changes (in XML) into the app config file.
It's amazing that a task which used to consist of :
create instance of ini file class
read/write datetime/string/int/bool to particular section
release instance of ini file class
(literally three lines of code - 6 with a try finally block) has now become a process that an experienced programmer could very well waste 5-10 minutes on... and a process that he/she will undoubtedly have to replicate many times during the development of any project, potentially wasting hours of his/her time.
So the new ConfigurationManager class seems to be, in brief, a major disappointment in terms of it's versatility and usability. It's quite nice if all you want to do is store a name/value pair or a ConnectionString but as soon as you want to organize your configuration information (even just into sections like with ini files) it chokes productivity completely.
Best Regards,
James Crosswell
Microforge.net LLC
http://www.microforge.net
.
- Follow-Ups:
- Alternative Solution
- From: James Crosswell
- Alternative Solution
- References:
- Where to store config information?
- From: James Crosswell
- Re: Where to store config information?
- From: James Crosswell
- Where to store config information?
- Prev by Date: Re: Where to store config information?
- Next by Date: Re: Get properties on interface (runtime/reflection)
- Previous by thread: Re: Where to store config information?
- Next by thread: Alternative Solution
- Index(es):
Relevant Pages
|