Summary
ContentsXML serialization can be very easy in .NET. It is perfect for managing configuration files or small sets of data that don't need a full database solution.
The following code sample can be copied directly into a Visual Studio console project. Create the console project first. Then delete everything in the Class1.cs file replacing it with the code below. Compile and run.
So, the gist of it is this. Create a configuration class that will hold all of your configuration information. Then use .NET's built in XML Serialization features to read and write the XML configuration file.
One thing to watch out for when managing configuration files is versions. You will eventually realize that you wanted to store more variables in your configuration file or perhaps remove some that were there before.
For example, suppose your configuration class has a variable called Var1. Later on you realize you want to add a Var2, but there are already old config files out there that don't have a Var2. .NET will do a pretty good job of reading the XML file anyway and filling the properties it can find. In our example, there will be no value for Var2 in old XML files, so the Var2 property will be whatever it was initialized to.
But .NET may not be able to handle every situation you may face. You may find you need to do some customization, in that case it will be critical that you know the version number of the configuration file so that you can ensure it is parsed correctly. Anyway, versioning is a good practice. I learned the hard way, but you can benefit from my mistakes.
Simple Configuration File Using XML Serialization
Contentsusing System;
using System.IO;
using System.Xml;
using System.Xml.Serialization;
namespace Cambia
{
class MainClass
{
[STAThread]
static void Main(string[] args)
{
Configuration c = new Configuration();
c.StringItem = "My Config";
c.IntItem = 2456;
Configuration.Serialize("config.xml", c);
Configuration c2 = Configuration.Deserialize("config.xml");
Console.WriteLine(c2.StringItem);
Console.WriteLine(c2.IntItem);
}
}
#region -- Configuration Class --
/// <summary>
///
///
///
///
/// </summary>
[Serializable]
public class Configuration
{
int _Version;
string _StringItem;
int _IntItem;
public Configuration()
{
_Version = 1;
_StringItem = "";
_IntItem = -1;
}
public static void Serialize(string file, Configuration c)
{
System.Xml.Serialization.XmlSerializer xs
= new System.Xml.Serialization.XmlSerializer(c.GetType());
StreamWriter writer = File.CreateText(file);
xs.Serialize(writer, c);
writer.Flush();
writer.Close();
}
public static Configuration Deserialize(string file)
{
System.Xml.Serialization.XmlSerializer xs
= new System.Xml.Serialization.XmlSerializer(
typeof(Configuration));
StreamReader reader = File.OpenText(file);
Configuration c = (Configuration)xs.Deserialize(reader);
reader.Close();
return c;
}
public int Version
{
get { return _Version; }
set { _Version = value; }
}
public string StringItem
{
get { return _StringItem; }
set { _StringItem = value; }
}
public int IntItem
{
get { return _IntItem; }
set { _IntItem = value; }
}
}
#endregion
}Output from running the above console application
ContentsHere's what the XML configuration file looks like
Contents<Configuration>
<Version>1</Version>
<StringItem>My Config</StringItem>
<IntItem>2456</IntItem>
</Configuration>