How to ensure registry cleaners don't wipe out your application settings?

[chasetoys]

So I want to place some entries in HKEY_CURRENT_USER.SOFTWARE.MICROSOFT.WINDOWS.CURRENTVERSION.MYAPP\

It's configuring a system property so I feel it belongs here.... my fear is those registry cleaners.... how do you make sure they don't wipe out your application data?

Thanks

[wildfrog]

It's configuring a system property so I feel it belongs here....

What system property?

I'm sure if you add your own registry settings they bolong in a location like:

HKEY_LOCAL_MACHINE/Software/YourCompany/YourProduct/
- or -
HKEY_CURRENT_USER/Software/YourCompany/YourProduct/

Don't you agree?

- petter

[sreehari]

why do you think tat registry cleaner would randomly delete your entry into the resistry . f your entry is an valid entry it would not delete them. here are a few links that explains how registry cleaners work.
Registry Drill
Registry Cleaners and Tools

[chasetoys]

So I'd like to know whether I should be putting it in the CURRENT_USER hive, or the LOCAL_MACHINE hive.

What's more common?

Secondly, what is an installation program I can use to install registry key entries (that is free, and super easy to use)

[sreehari]

Here are some installers that you can use
Microsoft Visual Studio Installer 1.1
Inno Setup
Wise Solutions
NSIS (Nullsoft Scriptable Install System)

for installn the registry keys ...why not do it programatically ? check the Registry Functions

[chasetoys]

I definitely *WANT* to do it programatically, however, how do you deal with issues of path. I have an .exe that needs to be in Windows, and it won't know where the user installed the rest of the data files (should be in C:\Program Files\MyApp) but there is certainly no gaurantee.

So how else would you address this problem? Thanks!

[Amn]

If you are an aware programmer, you would put all the settings which are the same for all users i.e. machine level settings, settings which have to do with program configuration regardless of which user runs it, under HKEY_LOCAL_MACHINE. All personal user preferences related to your program have to go under HKEY_CURRENT_USER. That way your program will behave fine, and Windows will like it

[chasetoys]

If you are an aware programmer, you would put all the settings which are the same for all users i.e. machine level settings, settings which have to do with program configuration regardless of which user runs it, under HKEY_LOCAL_MACHINE. All personal user preferences related to your program have to go under HKEY_CURRENT_USER. That way your program will behave fine, and Windows will like it

Sounds like a solid plan, and that's what I'm doing.

However, do installations typically write keys to the registry? Because I really need to write a couple of keys to the registry at that time. But if there is some way to do it programatically, please let me know.

Thanks!

[Amn]

Yes, last time i fired up Installshield thing, it had option of scripting registry writing schemes. But i really hate Installshield, it is such a benemoth of an app, and all for nothing. Amuses me how small software uses minutes to install because of Installshield overhead. Try Nullsoft install system It is tiny, and does most of the same job, including registry writing. But to tell the truth, you decide yourself which install system to use, or even whether to write your own, which is an option too.