I have an MSI to fix a Winsock error and need to roll it out after people have a proxy client uninstalled (i messed the installer up and removing it breaks winsock completely [;)]).
The issue comes in if they have a newer proxy client installed, i need the winsock msi not to install.

I need the winsock msi to check to see if the newer proxy client is installed, and if so cancel.

Is there something I can add to the MSI to run this check?
I have the product code for the newer proxy client if that helps.

Many thanks in advance for your help.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


You could use a "launchcondition" combined with an "AppSearch" (or an "Upgrade" table entry for that matter).

Or you could give your MSI the same "ProductCode" (but different "ProductVersion") as the old MSI. In this case, the installer won't install the new MSI unless you specify a "REINSTALL".
Answered 06/18/2007 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
Hi Wise

Thanks for the post.

I prefer the idea of using a launch condition and app search as it sounds like it will cause less issues when the new proxy client is installed.

Can you give me more info on how to do that please - sorry i am a noob.

Thanks again

Answered 06/18/2007 by: chappers77
Senior Yellow Belt

Please log in to comment