05-07-2010, 04:18 PM
I have been searching for an answer on Google, but can't quite find one. I have a 2005 .NET deployment project that installs a DLL I wrote. However, for this to work two other Microsoft programs must be installed. They are not packaged with Windows ordinarily, and they are not detected as Dependencies. I have the two .msi files for these programs, and I was trying to find a way to, at the end of the installation of my program, call these two other .msi files and run their installations.
Anyone have any ideas?
05-07-2010, 07:17 PM
I assume you are using Visual Studio's built in deplotment projects to build your setup file?
I use InstallShield myself and would try to find the appropriate distributable the put into the file.
Eitherway you can execute an msi from within a setup project with the right command line options with "msiexec" to install them. But this is usually frowned upon as it can produce unreliable results for Windows Vista/7 UAC elevation and also unreliable uninstallation (or even detecting a successful installation).
What are the two dependancies you're talking about?
05-07-2010, 07:23 PM
Yes, I am using VS's deployment project. I am including extensibilityMSM.msi and lockbackRegKey.msi. These are necessary to install MS Office plugins on machines that don't have Visual Studio installed on them. Right now, I think I may just go with creating a batch file with msiexec "filename" for each of the two dependencies. This program is only getting installed on I believe 4 different machines at our company. I was just curious if there was a way to do this with VS's built-in deployment project.