using System;
using System.Collections;
using System.Xml;
using System.IO;
using System.Reflection ;
using System.Windows.Forms;
namespace Compact.Configuration
{
public class ConfigurationSettings
{
const string sectionTag ="appSettings";
public static Hashtable AppSettings
{
get
{
Hashtable settings = new Hashtable();
string assemPath=Assembly.GetCallingAssembly().GetName().CodeBase;
string configFilePath=assemPath+".config";
XmlDocument cfgDoc = new XmlDocument();
FileStream fs=new FileStream(configFilePath,FileMode.Open,FileAccess.Read);
cfgDoc.Load(new XmlTextReader(fs));
fs.Close();
XmlNodeList nodes=cfgDoc.GetElementsByTagName(sectionTag);
foreach(XmlNode node in nodes)
{
foreach (XmlNode childNode in node.ChildNodes)
{
XmlAttributeCollection attributes =childNode.Attributes ;
settings.Add(attributes["key"].Value ,attributes["value"].Value);
}}
return settings;
} } } }
--now in your class, we only need to add a using declaration: using Compact.Configuration ;and we can get our settings exactly as one would expect to do:
System.Windows.Forms.MessageBox.Show(ConfigurationSettings.AppSettings["Item1"].ToString());
You also might want to advise readers that if they expect their XXX.exe.config file to be deployed, they'll need to set its Build Action to "Content". Also, be advised that these implementations read through the entire Xml configuration file every time a setting is requested, so for apps with a lot of configuration elements one might want to consider the use of some sort of caching strategy.