MST to include Exe file
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
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
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
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'.
Also, this is completely the wrong forum for your post. It belongs in 'Package Development'.
Posted by:
RayCon
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
WSPPackager
14 years ago
Posted by:
RayCon
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
anonymous_9363
14 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.