Member Avatar for Toulinwoek

Can anyone offer any advice on how to go about setting up the ability for a program to allow a user to set or change configuration options?

I can create a form with certain options, but how do I store the selections? In a database? XML file? In the Registry?

Any help would, as usual, be much appreciated, but a solid explanation of the concept is what I'm really seeking, and if anyone can provide a link to a site where I can study the concept would be ideal.

  • 4 Contributors
  • 7 Replies
  • 257 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by Toulinwoek

Dani AI

Generated

A few practical, low‑risk steps to make this work well long term (builds on ideas from , and without repeating their snippets).

Start by defining a typed "configuration contract" (a single class or small tree of classes) that lists every setting, its CLR type, a sensible default and whether it is per‑user or machine‑wide. Treat each setting as data, not ad‑hoc text. That makes validation, migration and unit testing straightforward.

Pick storage by scope and sensitivity. For non‑secret user settings a per‑user file under %APPDATA% (or ProgramData for machine settings) is portable and easy to back up. For secrets do not put raw passwords in files — use the OS credential store or DPAPI. For centralised/shared settings use a database or service. Avoid hand‑rolled text parsing for anything more than trivial toy data; use your platform serializer (XML/JSON/binary) so the library handles reading/writing and typing.

Make reads/writes robust: load on startup with try/catch, fall back to defaults if parse fails, and log the error. Save atomically (write a temp file then replace) so crashes never leave a half‑written file. Example atomic write pattern:

var temp = path + ".tmp";
File.WriteAllText(temp, serializedData);
File.Replace(temp, path, null); // NTFS atomic replace; or move after delete if not supported

Also consider runtime reload (FileSystemWatcher) if external edits are allowed, and prevent concurrent writers with a short mutex or file lock. Add a version tag to your config root and include simple migration code so new releases can upgrade older files. Finally, make the file human readable (comments or clear names) so admins can inspect or hand‑edit, and keep a "reset to defaults" option for recovery.

If you want, start by listing the settings you need and whether they are secrets/shared/user‑specific; that list drives the storage choice and serialization style.

Recommended Answers

All 7 Replies

Member Avatar for campkev

What kind of program is this? A windows app or web app.
If it is a windows app, I would use an ini file (or xml if you want). Just write the configuration changes to it and then read it when program opens. I prefer to stay away from the registry unless absolutely necessary.

if this is a web app, you would probably need to either use a cookie or a database.

Member Avatar for Toulinwoek

It's a windows app, and I'd lean toward an XML file myself, but I'm not sure how to implement that functionality. Am I correct to assume that reading the file would require some sort of parsing, or would the app just "understand" what it reads on startup because it wrote it?.

I don't know if I'm just storing a list of parameters and values, variables or something else. I also don't know what code I would write to even cause the app to read such a file (the functionality may be automated, but I just haven't found it yet). I'll of course keep digging, but I'll accept help!

Member Avatar for campkev

I don't think it is automated.
You will need to create a file reader, read the file in and then parse it.

Here is a code snippet of something i was working on.

private string stringA;
private string stringB;
private string stringC;
OpenFileDialog fd = new OpenFileDialog();
			fd.ShowDialog();
			FileStream f= new FileStream(fd.FileName, FileMode.Open, FileAccess.Read);
			StreamReader sr = new StreamReader(f);
			string strTemp = sr.ReadLine();
			while(strTemp != null)
			{
				switch (strTemp)
			 {
					case("<optionA>"):
						stringA = sr.ReadLine(); //reads in the next line after opening tag and sets it to stringA
						sr.ReadLine(); // gets rid of the closing tag
						break;
					case("<optionB>"):
						stringB = sr.ReadLine(); //reads in the next line after opening tag and sets it to stringB
						sr.ReadLine(); // gets rid of the closing tag
						break;
					case("<optionC>"):
						stringC = sr.ReadLine(); //reads in the next line after opening tag and sets it to stringC
						sr.ReadLine(); // gets rid of the closing tag
						break;

			 }
				strTemp =sr.ReadLine();
						
			}
			sr.Close();

The xml file would need to look like:

<optionA>
true
</optionA>
<optionB>
false
</optionB>
<optionC>
true
</optionC>

hope this gets you started

Member Avatar for tayspen

i would also like to know how to do this....

Member Avatar for Toulinwoek

Yeah, thanks campkev.
That's a good start; at least I can visualize the concept. I'll need to do a bit more study into file readers and parsing though.
As always, I'll try to post my progress so others who might be at the same level I am can benefit.

Member Avatar for cambia

How to best manage configuration information will depend on your situation, but XML is not a bad way to go in many cases. You can create a Configuration class with all of your variables, then just serialize it to XML. It's simple.

Check out my article on this subject for more details and full code:

Cheers,
- Steve

Member Avatar for Toulinwoek

How to best manage configuration information will depend on your situation, but XML is not a bad way to go in many cases. You can create a Configuration class with all of your variables, then just serialize it to XML. It's simple.

Check out my article on this subject for more details and full code:

Cheers,
- Steve

Thanks, I have looked at it and will spend some time going over it later this evening. Very helpful site, by the way.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.