Check another installed application before msi runs

Question

I have created simple msi, now I want to check another application is installed on the client machine or not before my msi runs.

because the application what I have created has a dependency of another application. If my application has to work on the client machine then that machine should have another application installed.

Lets say a.exe has a dependency on b.exe.

I have created msi for a.exe, when I run msi for a.exe in client machine then this msi has to detect whether b.exe is isntalled in client machine or not. if not then terminate the msi isntallation

How do you create the installer, do you use visual studio package and deployment project? — Reza Aghaei, Mar 21 '16 at 16:15
You may find [this post](http://stackoverflow.com/q/33493526/3110834) and [this one](http://stackoverflow.com/questions/908850/get-installed-applications-in-a-system) helpful. — Reza Aghaei, Mar 22 '16 at 15:51

score 2 · Answer 1 · answered Mar 23 '16 at 14:49

If the another application was installed using MSI,

you can use Upgrade mechanism.

WiX:

<Upgrade Id="<UpgradeCode of the another App>">  
   <UpgradeVersion Property="PREVIOUSINSTALLEDAPP" />
</Upgrade> 

<Condition Message="Please Install another application">
  <![CDATA[PREVIOUSINSTALLEDAPP]]>
</Condition>

And ensure that FindRelatedProducts sequenced before LaunchConditions.

score 0 · Answer 2 · answered Mar 23 '16 at 18:08

If you used the Visual Studio Installer then your options are somewhat limited. If the install of B creates a registry key then the Search Target Machine in your setup can search for that key and use it as a launch condition. If you have the MSI for B then you can open it with Orca from the Windows SDK kit and look at the Component table and find the Component Guid for (say) the executable that is installed. Again, that can be used in Search Target Machine for a Windows Installer search and a launch condition.

In general these checks work better in the actual app than in the install. You're forcing an install order that may be pointless because your install doesn't depend on B, only your application. So it's more friendly to allow any install order and put the check in your app saying it needs B to work if it's not installed. If the user uninstalls B does that mean your app will just crash because the only checking is at install time?

Check another installed application before msi runs

2 Answers2