No, it's a Windows application, but yes, I'll probably use XML.
It seems the logical way to go.
If it is not a .NET application, then the recomended way is the registry.
Adding a full xml parser just to load a config file might be a bit too much.
If you use one already for other functions in the application, then this
should be ok.
A warning if you have a Windows application and config files (.ini or .xml):
respect the user/system folders, test the functionality as non-admin.
You should store user settings in the user folder, and system setting
(that can be changed by the admin only) in a common place, read-only for
a normal user.
Good places for user settings:
"C:\Documents and Settings\<User>\Application Data\<Company>\<App>\"
"C:\Documents and Settings\<User>\Local Settings\Application
Data\<Company>\<App>\"
Good places for system settings:
"C:\Documents and Settings\All Users\Application Data\<Company>\<App>\"
And do not hard-code this, use SHGetFolderPath :-)
--
Mihai Nita [Microsoft MVP, Windows - SDK]
------------------------------------------
Replace _year_ with _ to get the real email
