I have many packages that are exe's that I created with wise script. I have some custom reg settings and shortcuts I would like removed when a user removes the program from add/remove programs. Is there a way with a wise script wrapper to hide the vendors MSI dialog from add/remove programs and include a entry that points to my custom uninstall script? I have tried changing the uninstall string to point to my uninstall script but they always seem to ignore it and use the vendors MSI removal. Any suggestions?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Do you mean that you have WiseScript EXEs serving as *wrappers* to the vendor MSIs? The first question which springs to mind is, why? Ignoring that, you state that you want to hide the entry from ARP (use the ARPSYSTEMCOMPONENT property) but that the uninstall entry should call a custom script. That would only apply for use with ARP: if the WiseScript is going to uninstall the wrapped MSI, then surely you don't need an uninstall string entry? Just have the script shell out to your uninstall script. Or have I misunderstood your question?
Answered 02/28/2008 by: VBScab
Red Belt

Please log in to comment
0
so I got the vendor msi hidden from ARP with the SystemComponent setting but how can I get a entry in ARP that points back to run my setup.exe
Answered 02/28/2008 by: stealthkd
Yellow Belt

Please log in to comment
0
I would be more inclined to hide the Wise Script add/remove entry and leave the MSI entry as is
The wise script doesn't do anything but install the app
If you want to remove the app just use the native windows installer control panel method.
Answered 02/28/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
but what if your wise script does your uninstall if the install exists and it removes custom shortcuts and does registry changes. I dont have a entry in ARP for my setup.exe but I want one
Answered 02/28/2008 by: stealthkd
Yellow Belt

Please log in to comment
0
SSSSSSSSSoooooooooo....let me get this straight....you want to hide the ARP entry but have an ARP entry pointing to your Setup.EXE? Are those two requirement not mutually exclusive?
Answered 02/29/2008 by: VBScab
Red Belt

Please log in to comment
0
Ok, WiseScript Wrapper (setup.exe) kicks off MSI and does some shortcut moves and registry entry. If you run my setup.exe again it does a removal of the MSI, shortcuts, and has some registry entries. Setup.exe does not get an entry into ARP only the MSI does. If you use the MSI entry in ARP to remove it does not remove my shortcuts or add my registry entries. So I want to hide the MSI entry in ARP so users can't use it and I want to add an entry that runs my setup.exe so the app removes the way I need it too.

Reason: My company requires certain shortcuts,logs, and registry entries when a program is added or removed from a system. Normally transformable some MSI's will not allow Wise to open or create transforms for them (Citrix Client for example).

I figured out a soulution last night but I am not sure it's the best one. I would like to be able to do all this in WiseScript if possible.

I add a key to uninstall string GUID SystemComponent =1. That hides the MSI in ARP.
I create a MSI in Wise that does nothing but give me an entry in ARP with the Application name and information, I set the remove to kick off embeded VB Script that kicks off the uninstall of my Setup.exe. I add this MSI to the original Setup.exe WiseScript to be run silently.

MSI is only 340kb in size so it doesnt bother me to much and now I have a template to do more with. Is there an easier way, could this have been done in Script Editor on my original setup.exe without creating a special MSI for the remove?
Answered 02/29/2008 by: stealthkd
Yellow Belt

Please log in to comment
0
The use of Setup stubs is fraught, unless you have stringent documentation and/or source control, in that subsequent packagers come along to make changes and - in general, from my experience, - without those things, they will tend to simply start again from scratch.

Why not:

- set your MSI to be invisible to ARP
- include the registry settings and shortcust therein but mark them to not be uninstalled
Answered 03/01/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity