To be honest, I often bypass Microsoft’s approach to saving data in config files because most of my apps only need to use application level settings. User settings in a corporate context for me would typically be stored in a database table. So I often revert to simpler, more straightforward techniques such as:

1) Create a datatable to hold the settings, then save as and retrieve as xml since this is built right into the datatable methods. Be sure you save with schema such as ….

dt.WriteXml(Path.Combine(sAppPath, “myappdatafile.xml”), XmlWriteMode.WriteSchema)

The sAppPath can be obtained with something like …

sAppPath = My.Application.Info.DirectoryPath

Datatables are great because you can easily loop through the rows, have as many values per row as needed and even pass single rows to methods as a DataRow.

2) Use the old tried and true INI file approach such as a simple text file with Name=Value pairs on each line. You can retrieve this file into an array of strings with single line such as….

Dim myappdata() As String = File.ReadAllLines(sDataFilePath)

Then loop through the array and split each line at the = character and store into a hashtable, list or object array. This is so easy to read and write to. Microsoft wanted to create a generic and universal approach to saving data and it does work but can often require much time to learn all the nuances. But if your needs are simple, then designing your own approach that you have complete control over.

I did a custom myself as well. Thiking the base must be alumniium and 3x 80mm fans to blow cold air in from the base.

Then additional fans at the rear to help extract air out from the two vents.