/build/static/layout/Breadcrumb_cap_w.png

Problems registering an .exe file using WISE 6.1.0.281 for packing into an MSI

Hi Guys,

Ive been asked to create a package in WISE 6.1.0.281 that updates an already installed app.

Now im a newbie when it comes to packaging so if this is a stupid question Great! I hope its answered quickly :D

I have been given a .dll and .exe to package up as a "postfix", however both the .dll and .exe needs to be registered. The .dll is no problem but I do not know how to register a .exe for packaging in wise.

When creating the package itself I copy the .exe file to the correct location and run the following command:
"filename.exe /regserver"
This registers ok.

When it comes time to edit the package in Wise GUI (details of the file) I get the following error:
"This version of wise cannot register .exe files"

After compiling, the MSI package itself fails when I ran it for a test:
"pathname\filename.exe failed to register. HRESULT -2147024769

Am I missing something obvious? Can .exe be registered in wise at all? Do I need to upgrade wise to process this command?

Im not really how to continue from this point an any help would be appreciated.
Thanks,

0 Comments   [ + ] Show comments

Answers (1)

Posted by: AngelD 13 years ago
Red Belt
0
Remove the filename.exe from the SelfReg table and author a custom action executing "<path to filename.exe> /regserver" on the condition 'Not Installed'. You will need to unregister the file during uninstall; use the /unregserver switch instead with the condition 'REMOVE=~"ALL"'.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ