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: Uninstalling delete System Path if I've updated it.
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
‎Apr 29, 2010
04:33 PM
Uninstalling delete System Path if I've updated it.
I’ve have a problem I can’t seem to find a solution to and I’m looking for advice.
Product: InstallShield 2010
Project type: InstallScript MSI
Problem:
In my project I have an option that dumps dlls to location not in the product directory or the system directory. When I do this I also need to add the location of these files to the System Path, which I do using the function RegDBSetKeyValueEx(). change to the registry is done programmatically only.
My problem is that when this option is used and when I my product is un-installed the System Path is deleted. End users then find the next time the boot up that all sorts of ugliness happens because the system path is gone. Any suggestions?
Product: InstallShield 2010
Project type: InstallScript MSI
Problem:
In my project I have an option that dumps dlls to location not in the product directory or the system directory. When I do this I also need to add the location of these files to the System Path, which I do using the function RegDBSetKeyValueEx(). change to the registry is done programmatically only.
My problem is that when this option is used and when I my product is un-installed the System Path is deleted. End users then find the next time the boot up that all sorts of ugliness happens because the system path is gone. Any suggestions?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 29, 2010
05:02 PM
If you can use the MSI Environment Variables view instead, that gives you some uninstallation options; or you might see if per-app paths will help.
Otherwise, you can wrap your registry script between Disable(LOGGING) and Enable(LOGGING) to keep the information there forever, or see KB Q107382 for a more sophisticated technique.
Otherwise, you can wrap your registry script between Disable(LOGGING) and Enable(LOGGING) to keep the information there forever, or see KB Q107382 for a more sophisticated technique.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2010
01:34 PM
Thanks! That works great!