Ok...a little open source piece of software called NUnit is giving me more issues that automating Office installs...

If you step through the install manually, it works just fine. We're changing no defaults, so we throw a /qb after it....it installs the program, but........no shortcuts (desktop or start menu). Try other switches, same result. Build a transform to step through, same result.

The more I look at it, it looks like the shortcuts don't get added to the desktop or start menu until the actual final screen comes up where you click 'finish'. This is where I think the switches are cutting off the install.

Anyone have any ideas of what to look for in the actual MSI script itself? I'm good with tweaking a lot of little things in the MSI, but not so much with the actual script unless i'm adding something. I'm hoping I might be able to rearrange the icon creation a step earlier.

Any help is greatly appreciated!
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Sounds like the shortcuts are added by a custom action from the UI sequence (InstallUISequence table) which will not be executed during basic mode
Answered 06/11/2008 by: AngelD
Red Belt

Please log in to comment