Dave_Gleason
asked on
Can a VS Setup and Deployment installer trigger an external install.
In VS2008, is there a way to trigger an external install during the original one. Here is what I am tring to do.
I have an application that gets installed using a Setup and deployment project. (Setup.exe)
I want at the end or near the end to trigger another Setup.exe (located in a slightly different directory to install some NI software (also Setup.exe). Their redistributable doesn't seem to include just one MSI, but rather several. Thats why I want to trigger the setup.exe.
I have tried to do this using Custom Actions (both Install and Commit) to trigger the other install and that seems to start ok, but never finishes. I think the windows installer is using a mutex to prevent the second installer from really getting going because it thinks the original installer isn't complete.
I have tried to go down the route of creating an installer class but I didn't get very far with that because I could only get it to work with MSI not bootstrappers as shown below.
( System.Diagnostics.Process .Start("MS IEXE.EXE", "/i """ & savedState.Item("OtherMSIP ath").ToSt ring & """ /qb"))
Any help is greatly appreciated.
Dave
I have an application that gets installed using a Setup and deployment project. (Setup.exe)
I want at the end or near the end to trigger another Setup.exe (located in a slightly different directory to install some NI software (also Setup.exe). Their redistributable doesn't seem to include just one MSI, but rather several. Thats why I want to trigger the setup.exe.
I have tried to do this using Custom Actions (both Install and Commit) to trigger the other install and that seems to start ok, but never finishes. I think the windows installer is using a mutex to prevent the second installer from really getting going because it thinks the original installer isn't complete.
I have tried to go down the route of creating an installer class but I didn't get very far with that because I could only get it to work with MSI not bootstrappers as shown below.
( System.Diagnostics.Process
Any help is greatly appreciated.
Dave
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Seems like the custom action can't call another installer (because the first isn't complete). If I place the custom action at the Install or Commit level an error is thrown during install.