Hi All,

I have application called "Microsoft Streets and Trips 2008" this application is cashing 6 msi's in installer and 3 msi's don't have any files and registries in it.
So i am not getting which one is main msi in this and to which msi I have create transform
Suggest me the ways of diffrentiating the two msi's
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
Either, run the install with a log (IIRC, MS's Setup executable takes an argument to create a log) or run it in parallel with ProcMon. When you see the first 'Welcome' screen, open the log or check ProcMon's output to see which file it's opened.

As for the MSIs with no files or registry entries, my guess would be that they have a bunch of Custom Actions which call DLL functions (almost certainly InstallShield functions, since some divisions of MS are in love with IS) or VB Scripts, or that they contain Merge Modules (unlikely, but possible - it wouldn't be the first time I've seen that).
Answered 02/07/2008 by: VBScab
Red Belt

Please log in to comment
0
Hi VBScab,
Yes exactly the empty MSI's have only custom actions, so do you mean i can use these custom actions in the main MSI and Knock off the empty MSI.
Answered 02/07/2008 by: noorameen
Senior Yellow Belt

Please log in to comment
0
No, that isn't what I mean at all! Where did you get that idea from?

Never, never, never, never, NEVER mess with vendor MSIs unless you absolutely have to (unlikely). This mantra scores treble for Microsoft MSIs. Use transforms to apply changes to vendor MSIs.
Answered 02/07/2008 by: VBScab
Red Belt

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