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
- :
- Don't display in Add/remove
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 19, 2011
12:53 PM
Don't display in Add/remove
We are using AdminStudio 10 and InstallShield 11. I have created a new .ISM script. All this script does is create 1 registry key. I have compiled this into a single .EXE file. Each time I run this .EXE it of course spawns an .MSI which is fine. But.....since it's a .MSI it creates a new entry in Programs and Features and we don't want that. If all I want to do is create a custom "script" using the InstallScript internal language I don't want it adding an enter into Programs and Features. I don't see anyplace to prevent this entry.
How do you create an InstallShield .ism script/project and have Not create an entry in Programs and Features?
How do you create an InstallShield .ism script/project and have Not create an entry in Programs and Features?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 19, 2011
01:05 PM
you can set the Windows Installer property ARPSYSTEMCOMPONENT to 1 in the Property Manager in a Basic MSI project to hide ARP entry
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 19, 2011
01:17 PM
Thanks for the info. Question for you: I used Wise Script Editor for years which was (and still is) a great scripting tool. When you need to create a script that does a lot of custom stuff (check the reg, compare file versions, write custom logs to a server etc....etc...) do you think InstallShield is good for that?
Thank you.
Thank you.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 19, 2011
01:26 PM
rrinblue22 wrote:
you can set the Windows Installer property ARPSYSTEMCOMPONENT to 1 in the Property Manager in a Basic MSI project to hide ARP entry
So that did not work. I set ARPSYSTEMCOMPONENT=1 and recompiled. When I ran my setup.exe it still created an entry in Programs and Features.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 20, 2011
02:33 AM
Hello,
lets look in the IS-Help.
There is all about ARPSYSTEMCOMPONENT property.
Regards
Jan
lets look in the IS-Help.
There is all about ARPSYSTEMCOMPONENT property.
Regards
Jan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 21, 2011
05:00 AM
Hey hh1234.... I think all the task which you mentioned can still be achieved using InstallShield.start using InstallShield and you would feel the difference.
For me, InstallShield is very helpful and provides the flexibility to compile scripts to achieve complex task for rest things there's built in functionality........:)
For me, InstallShield is very helpful and provides the flexibility to compile scripts to achieve complex task for rest things there's built in functionality........:)