This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Writing Per-User Registry Keys
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2007
08:36 PM
Writing Per-User Registry Keys
I have a Basic MSI installer and I am working to make it Vista compatible and still work with Win 2000, XP, and 2003. Right now it works with Vista, but not for the others. All the research I have done for the past couple weeks has not gotten me to where I need to be.
In my installer, six of the components have a registry value that needs to be written to HKCU. So, I can't do this at install-time, because I would be asked for admin credentials, and it would then be written to the Admin profile, which I don't want.
I've read that the thing to do is install these components on first use. Fine, but I don't want this to be done by the user clicking on a shortcut. I have six components that this needs to be done for and having six shortcuts in my program group seems silly and an aggravation for the user.
In my Windows app, there are six menu items that correspond to the six components in the installer. What I would like is that when the user first clicks on one of these menu items, the installer would then run and install that component's files and HKCU registry entries. Some threads I have read makes me think this is similar to an Auto-Repair, which I've never done.
Is this possible? If so, can someone point me in the right direction? If not, what do people usually do in this situation?
In my installer, six of the components have a registry value that needs to be written to HKCU. So, I can't do this at install-time, because I would be asked for admin credentials, and it would then be written to the Admin profile, which I don't want.
I've read that the thing to do is install these components on first use. Fine, but I don't want this to be done by the user clicking on a shortcut. I have six components that this needs to be done for and having six shortcuts in my program group seems silly and an aggravation for the user.
In my Windows app, there are six menu items that correspond to the six components in the installer. What I would like is that when the user first clicks on one of these menu items, the installer would then run and install that component's files and HKCU registry entries. Some threads I have read makes me think this is similar to an Auto-Repair, which I've never done.
Is this possible? If so, can someone point me in the right direction? If not, what do people usually do in this situation?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 19, 2007
10:54 AM
I ask this because Microsoft does this with some of their programs.
My theory is that in my app, I could check if the registry entries are there. If so, perform the function. If not, call msiexec.exe with some parameter to install that component's files and registry entries.
I'll see if there is such a parameter to do this.
My theory is that in my app, I could check if the registry entries are there. If so, perform the function. If not, call msiexec.exe with some parameter to install that component's files and registry entries.
I'll see if there is such a parameter to do this.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 19, 2007
02:03 PM
That theory didn't pan out.
To state it simply, I need to install a component that has files and HKCU per-user registry keys at first-run. Supposedly the way to do this is by triggering an auto-repair. If one of the files is not there, the auto-repair is supposed to be triggered. But I haven't figured out how to do this yet.
To state it simply, I need to install a component that has files and HKCU per-user registry keys at first-run. Supposedly the way to do this is by triggering an auto-repair. If one of the files is not there, the auto-repair is supposed to be triggered. But I haven't figured out how to do this yet.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 19, 2007
05:16 PM
Can your application do this instead of the install? It seems like the application could check either when it first starts or when the user clicks one of the six menu items whether this is the first time. If "yes" then create the registry keys.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 19, 2007
05:46 PM
I see what you mean. I'll try that and see what happens. Thanks.