R – Is There Any Reason Not To Use The Windows Registry For Program Settings

configurationregistrywindows

To me its a no-brainer. The settings for my program go into the Windows Registry. After all, that's what it's for, isn't it?

But some programmers are still hesitant in using the Registry. They state that as it grows it slows down your computer. Or they state that it gets corrupted and causes your computer to malfunction.

So they write their own configuration files, or may use the INI files that Microsoft has depreciated since a few OS's ago.

From what I hear, the problems with the registry that occurred in early Windows OS's were mostly fixed as of Windows XP. It may be the plethora of companies that make Registry Cleaners that are keeping up the rumors that "registry bloat" and "orphaned entries" are still bad.

So I ask, is there any reason today not to use the Windows Registry to store my program configuration settings?

Best Answer

  • If the user does not allow registry access, you're screwed.
  • If the user reinstalls Windows and he wants to migrate his settings, it's much more complicated than with a simple file
  • Working with a config file means your app is portable
  • Much simpler for the user to change a setting manually
  • When you'll want to port your app to other OS, what are you gonna do with your registry settings ?