Hi
I need some help, I am new to packaging. I want to create a new msi for an application. I have entered the serial number and made some administrative changes for our clients. I get this message ; non-advertised shortcut must be created for example cmd.exe in programs folder ........auto repair cannot be enabled for this shortcut. What does this mean?? At the end of the build I get an error message: Conversion stopped with one or more errors. when I check the log file it does not show me the error. I am using Admin Studio to repackage the msi for this application.
If anyone can shed some light on this it would be great, thanks in advance for all your help!
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
If you are using a vendor MSI, you should create a transform (.MST) with your modifications instead of altering the original MSI.
Answered 01/06/2012 by: pmarshbu
Orange Belt

Please log in to comment
0
Which tool are you using? Are you repackaging the app?
Answered 01/06/2012 by: mekaywe
Brown Belt

Please log in to comment
0
Hi thanks for you response
I tried to create an MST file however I cannot get all my changes, the MSI will only install so far. Is there somewhere I can read up on creating mst's, it seems fairly easy but I must be missing something??
I am using Admin Studio 10 and yes I would like to repackage the app with all my changes so the clients can use the app with no interaction. I would like the app to install with no user interface, just a progress bar.
Answered 01/06/2012 by: kathyp
Yellow Belt

Please log in to comment
0
Did you try to create a shortcut for a file which is not in your package?

After making what changes exactly are you receiving the message to create non-advertised shortcut? and auto repair cannot be enabled?
Answered 01/06/2012 by: mekaywe
Brown Belt

Please log in to comment
0
This is very confusing...

In one breath you're saying that you're re-packaging then you're saying that you're trying to create an MST for the MSI.

- If you're re-packaging a legacy (i.e. non-Windows Installer/MSI-based) installer then you should be able to incorporate everything you need into one, new MSI.
- If the installer is already MSI-based, you need to use InstallShield's Tuner application to create the MST.

Before you do anything, however, you should [Y A W N] download and digest Phil Wilson's 'The Definitive Guide To Windows Installer'. Packaging's learning curve is very steep and you will struggle until you have a firm grasp of the fundamentals.
Answered 01/06/2012 by: VBScab
Red Belt

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