Package
Hi,
I have a requirement where i need to install a .exe and .msi. Can any body suggest how to go about doing this?
As from VS studio installer we cannot add an msi. Have tried running .vbs and try to install the .msi from a msi. But "Another installation is in progress. You must complete that installation before continuing this one." is been thrown.
Please suggest
I have a requirement where i need to install a .exe and .msi. Can any body suggest how to go about doing this?
As from VS studio installer we cannot add an msi. Have tried running .vbs and try to install the .msi from a msi. But "Another installation is in progress. You must complete that installation before continuing this one." is been thrown.
Please suggest
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
francist
17 years ago
Not entirely sure what you are trying to do. The MSIEXEC process will only allow one installation at a time which is why you get the message 'Another installation is in progress'. There is a way of embedding or calling another MSI from within an MSI but it's limited and not 'best practice' as the embedded MSI cannot then be upgraded or patched in isolation i.e. it is treated as a single package.
Posted by:
Abs
17 years ago
Hi,
Well, i have a scenario where in i need to deploy and install to two separate products. one is a Win32 Cabinet Self-Extractor file and another is a .msi.
i mean one is A.exe and b.msi which i need to bundle together and install them on demand. i.e i need to install the A.exe and then B.msi.
Can you please suggest how i can go about doing this?
Well, i have a scenario where in i need to deploy and install to two separate products. one is a Win32 Cabinet Self-Extractor file and another is a .msi.
i mean one is A.exe and b.msi which i need to bundle together and install them on demand. i.e i need to install the A.exe and then B.msi.
Can you please suggest how i can go about doing this?
Posted by:
francist
17 years ago
Posted by:
Abs
17 years ago
Posted by:
sikkert
17 years ago
Posted by:
Abs
17 years ago
Posted by:
sikkert
17 years ago
A .msi file would not accepted in the MSI. Would throw up "Another installation is in progress." error.
I meant that since you don't want to modify b.msi, you should convert a.exe into a.msi. Then you can install a.msi, followed by b.msi, as two separate msi-installations. MSI is usually better for automatic deployment than exe, so you should you should transform a.exe anyway.
Posted by:
bheers
17 years ago
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.