For now, you pretty much have to "roll your own". There are a number of
online articles, many of which suggest the same thing you're planning to do.
Check
www.codeproject.com, as I recall seeing at least one there.
William's suggestion of .config for the app is fine if you're just reading
from the file at runtime. The framework doesn't have built-in support to
write/modify the file. There are articles/samples that show you how to do
that, but it's not terrribly safe -- if your app is in Program Files, a
standard "user" account won't have write/change privileges. You can use the
Environment type or Isolated Storage (either way) to store it in a
user-specific, permissions-safe location.
JD
"Dave Veeneman" <da****@nospam.com> wrote in message
news:uf**************@TK2MSFTNGP09.phx.gbl...
Is there a 'best practice' methodology for storing and retrieving
configuration data in C# Windows Forms applications? I'm talking about the
sort of stuff that went into INI files in the old days.
I'm planning to create a class to hold initialization information, then
serialize the class to the application directory to persist it. Any
better way to get the job done? Thanks
Dave Veeneman
DNL Systems