I have been using the following source configurations to manage the configuration of my projects for several years:
The first one imitates Java files .properties(a bunch of lines supergroup.subgroup.property=valuewith support for collections) and works great for many situations (I think this is best for small applications). This is useful for a very simple configuration.
The second is based on DataContractSerializer(and optionally XmlSerializer), which allows all the functions of the first with all the advantages of XML and less plumbing, to make it work. It's nice, but impractical and cumbersome to manage without an explicit user interface on top of it, to alleviate the headaches for teaching end users to change XML.
Both existing frameworks also marshal from POCOs without problems to allow access to configuration values ββthrough properties / fields (via manual / automatic serialization, respectively), so they are very easy to work with the developer.
Now, when I look at their options for including a database and good configuration, I'm looking for an alternative (preferably open source). I have no problem processing all my existing projects if I can reduce unnecessary code duplication and allow them access to the database and good configuration (in addition to their existing capabilities).
Any suggestions or should I redo my own to get the features I need?
, Nini, 2 , ( ). - ?
, :
- XML
- INI/Java-
properties - ( , MS SQL SQLite, MySQL , )
- ( )
- - API , .
- / , /.
, , , , , , .
UPDATE
System.Configuration , , , , . ( ), , XML: , .
- , , ( ). - , .
, 24 ( > 125 ), , , , , . , - .