Re: registry vs ini



I have developed an application with about 20 properties that I store in the
registry. Now I want to add additional items, i.e., about 10 to 50 or maybe
100 items depending on the user. Each item consistes of 2 to 5 properties.
The question is: should I store this information in the registry or rather
store it in an external file, and if so, in which location?
If the answer is to use an external file: Is it better to store all the
properties in this file, or should I store the properties in the registry
and the items in the external file. Or is it okay, to store all this
information in the registry?
Thanks for any help,
Sam

Just a personal opinion: I'd store all settings in an .ini file in the installation folder and try to make the program a no-install (just unzip the folder, double click the exe, and everything runs). That way, your client(s) can copy the program to a USB drive and take it to another computer with no problem.


.



Relevant Pages

  • Re: Final installation
    ... Saving the registry is part of the OS design. ... you might store it there. ... you'll need some form of a bootloader to handle loading the OS ...
    (microsoft.public.windowsce.embedded)
  • Re: Where are OEs settings stored?
    ... The key name is "Store Root" under ... export the registry to a text file and save. ... MS-MVP Outlook Express ... back door method to locate the message store ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Ini File vs Registry
    ... I have a class derived from CArchive and store my own version info at the start of the file. ... I tend to use the registry for execution-to-execution parameters which can be readily reconstructed from defaults. ... I do not know what a best practice is here. ... not specified where you would keep the .INI file. ...
    (microsoft.public.vc.mfc)
  • Re: dialogbox and Persistence
    ... In general you should store persistent data in the ... schemes etc. should go in the registry in HKEY_CURRENT_USER. ... should be stored to disk, able to be loaded by different users on the ... I forgot to mention that the Serialize code that I posted ...
    (microsoft.public.vc.mfc)
  • Re: Distributing application
    ... > rather than the system registry because for security reasons there's a ... you can make changes to the registry ... database there. ... user's section of the registry would be a good place to store the list. ...
    (microsoft.public.dotnet.languages.vb)

Loading