Hi,

I just created a MST using a vendor MSI. This vendor MSI require C++ component to be install before it can run.

For testing purposes I have install C++ manually to get it to run succesfully.

How do I include the C++ exe in the MST file so that the C++ exe run before the MSI does.

Your advise is much appreciated!

Ray
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're able to control the deployment, I'd suggest deploying the runtime separately. If you don't, e.g. if you're creating media for external usage, it might be best to create a merge module and include it that way.

Also, this is completely the wrong forum for your post. It belongs in 'Package Development'.
Answered 04/14/2010 by: VBScab
Red Belt

Please log in to comment
0
Sorry, I just join this forum.

Not sure how to get to the package Dev section yet.

It gets deploy by different team so we only give them the MSI/MST files.

I am new to packaging so still learning how to use MST.

Thanks!
Answered 04/14/2010 by: RayCon
Senior Yellow Belt

Please log in to comment
0
Not sure how to get to the package Dev section yet.The link to it is in my response.
It gets deploy by different team so we only give them the MSI/MST files.So you give them an MSI and MST for the runtime and an MSI and MST for the package.
Answered 04/14/2010 by: VBScab
Red Belt

Please log in to comment
0
Hi Ray,

I would go with vbscript or Wise script and controls the installation of exe and msi. First call the c++ exe and then call the MSI.

Regards,
WSP Packager.
Answered 04/14/2010 by: WSPPackager
Senior Purple Belt

Please log in to comment
0
Cool... So I don't need the mst file after all.

Put everything in the wise scripts?

I'll give it a go!

Thanks!
Answered 04/16/2010 by: RayCon
Senior Yellow Belt

Please log in to comment
0
EDIT:
Reproduced in post # 8. I don't know how I hadn't spotted this until now!
Answered 04/16/2010 by: VBScab
Red Belt

Please log in to comment
0
So I don't need the mst file after all.You might do, if any of your dialog choices are not the default. For example, most packages default to a 'Typical' install. If you want a 'Complete' install, you may need a transform to at least change the public property "behind" the relevant radio button. An d yes, I *know* you can do that from the command line but that's missing the point.

BTW, if, as I suspect, the "C++ component" you refer to is actually the C++ runtime, there's a very good case to be made for including it in your build...or you may want to consider creating a merge module, as I mentioned earlier in this thread. Since each r/t that I've seen ultimately extracts and executes an MSI anyway, converting it to an MSM should be a snap.
Answered 04/16/2010 by: VBScab
Red Belt

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