Re: Vista makes me crazy, please help.


"Dave O." <nobody@xxxxxxxxxxx> wrote in message news:uUU9FqMSJHA.4764@xxxxxxxxxxxxxxxxxxxxxxx

"MM" <kylix_is@xxxxxxxxxxx> wrote in message news:bq23i4t64ah3afm6rjru03jepg9f0qbncf@xxxxxxxxxx

I simply cannot see any
benefit for an app to use the Registry for storing interim session
data or default settings.

It keeps the data in one place in a consistent structure

I never saw an advantage to keeping totally unrelated data in a single place; if anything that just means that if a problem occurs you lose all info for all apps instead of just one set.

It avoids the problem of multiple INI files for different logins, your method would either require a complex INI or separate installations for each login.

It's hardly complex to have the filename or the section name contain the user ID if that's necessary or to place the INI under the user's app data folders. It's not that different than letting the OS use the current user to select the values to read.

It saves disc space by replacing myriad little files with a few big ones

The overhead of the registry index structure cuts into that but even if it still saves space it is a small advantage that is utterly swamped (IMO) by the advantages of the individual files.

As it (should be ) buffered it (should be) far faster.

There is some buffering on INI files as well and unless you are doing a LOT of reading and writing settings the speed just is not an issue.

Possibility: In-built simple parity based error correction
Possibility: History, allowing for rolling back or at least a level or two of undo

Lots of things could be done to improve INI (or even XML) file handling as well

Now all the above are what a "registry" should be, unfortunately, well you know the rest.......

Yes, it's not a great implementation but even if it were improved the basic concept of the single storage area for everything is just not a good one IMO. YMMV (and apparently does <g>) The registry is good for public info but inappropriate for internal app settings and data.


.

Relevant Pages

  • Re: Ini File vs Registry
    ... How do you manage the settings? ... dollars in hacking the OS to introduce the concept of registry ... Hard to migrate app ... but increasingly desktop developers are fighting it out ...
    (microsoft.public.vc.mfc)
  • Re: Disadvantages to peristing replication settings as text?
    ... I'd actually have the mobile app include a "settings" ... in the registry. ... derived the encryption algorithm. ...
    (microsoft.public.sqlserver.ce)
  • Re: .ini .dat or registry question
    ... > OTOH, I'd far rather help a user get the settings in an INI straight, than ... the INI API was obsolete. ... I've also read about the registry being frowned upon ...
    (microsoft.public.vb.winapi)
  • Re: Ini File vs Registry
    ... How do you manage the settings? ... dollars in hacking the OS to introduce the concept of registry ... Hard to migrate app ... with web apps and their no-install worries propositions. ...
    (microsoft.public.vc.mfc)
  • RE: Reg/INI Discussion from much earlier
    ... If it takes a noticable time to save the configuration data, you've either written the app wrong, or defined configuration data wrong. ... > in the event of an improper shutdown, the registry is NOT saved. ... > uncontrolable factor and the user wants to save his/her settings. ...
    (microsoft.public.vb.general.discussion)
Loading