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
- :
- Create setup which always installs
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 25, 2009
09:33 AM
Create setup which always installs
is it possible to create a setup package, which not only shows no add/remove in "software", but also installs always like a "new" installation?
thanks in advance
mary
thanks in advance
mary
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 25, 2009
11:52 AM
Hello Mary, using an InstallScript project type is the only way I know how to do it. You would set the Maintenance Experience in the Project Properties tab of the General Information view to "No uninstall or maintenance".
Hope this is what you were looking for!
Tim
Hope this is what you were looking for!
Tim
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2009
07:16 AM
Hi timstspry,
I'll give it a try and post the result as soon as possible!
Thanks
maryv
I'll give it a try and post the result as soon as possible!
Thanks
maryv
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2009
08:30 AM
It's possible to do it with an MSI, but it's not as "clean" as with InstallScript type. There are actions you can remove or condition not to run that will prevent Windows Installer from recognizing that the product is already installed. However, the Component codes still get written to the registry, and since the product they refer to isn't installed, they get orphaned.
Set the following so they don't run:
RegisterProduct
RegisterUser
PublishFeature
PublishProduct
Also, set the ARPSYSTEMCOMPONENT property to "1" so the install won't show in Add/Remove Programs.
I agree that you may be better off with an InstallScript type project, unless you have to support MSI for some reason, like supporting a push through Group Policy, that you can't do with an .exe.
Set the following so they don't run:
RegisterProduct
RegisterUser
PublishFeature
PublishProduct
Also, set the ARPSYSTEMCOMPONENT property to "1" so the install won't show in Add/Remove Programs.
I agree that you may be better off with an InstallScript type project, unless you have to support MSI for some reason, like supporting a push through Group Policy, that you can't do with an .exe.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2009
09:08 AM
Windows installer does support a multiple instance installation scenario.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 25, 2009
10:29 AM
thanks for all your suggestions...
i tested multiple instances and it suits my needs.
btw, i can't change the text in this dialog ... create new instance/change existing, right?
mary
i tested multiple instances and it suits my needs.
btw, i can't change the text in this dialog ... create new instance/change existing, right?
mary
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)