Are there any ways, such as using launch conditions, to stop the
installation when the version of Outlook does not match the version of
add-in?

Both setup.exe and msi can run through regardless the version of Outlook.

MS article "Deploying VSTO 2005 SE Solutions Using Windows Installer" only
talks about VSTO version.

VSTO or not, that article gives you all you need. You need to set up a
bootstrapper package condition that checks for Office/Outlook installed at
all and that the correct version is installed.

The article shows an ExternalCheck which calls ComponentCheck.exe with the
component code you want verify. The codes for Outlook 2003 and 2007 are
listed below that.

I use something a little different, I put an AssemblyCheck into the
InstallChecks node that looks for the Outlook public key token and a
version of "11.0.0.0" for Outlook 2003 or "12.0.0.0" for Outlook 2007. I
also use a RegistryCheck on
HKCR\CLSID\{0006F0#A-0000-0000-C000-000000000046}\ProgID, which is only
there if an Outlook PIA is installed.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Jason" wrote in message
...
Are there any ways, such as using launch conditions, to stop the
installation when the version of Outlook does not match the version of
add-in?

Both setup.exe and msi can run through regardless the version of Outlook.

MS article "Deploying VSTO 2005 SE Solutions Using Windows Installer" only
talks about VSTO version.

Checking PIA works. It is enough just checking PIA without checking Outlook.
PIA checking will not get through in all 3 possible cases:
1. Office is not installed at all
2. Office is installed but not Outlook
3. Outlook is installed but version does not match PIA

Thanks Ken.

"Ken Slovak - [MVP - Outlook]" wrote in message
...
VSTO or not, that article gives you all you need. You need to set up a
bootstrapper package condition that checks for Office/Outlook installed at
all and that the correct version is installed.

The article shows an ExternalCheck which calls ComponentCheck.exe with the
component code you want verify. The codes for Outlook 2003 and 2007 are
listed below that.

I use something a little different, I put an AssemblyCheck into the
InstallChecks node that looks for the Outlook public key token and a
version of "11.0.0.0" for Outlook 2003 or "12.0.0.0" for Outlook 2007. I
also use a RegistryCheck on
HKCR\CLSID\{0006F0#A-0000-0000-C000-000000000046}\ProgID, which is only
there if an Outlook PIA is installed.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Jason" wrote in message
...
Are there any ways, such as using launch conditions, to stop the
installation when the version of Outlook does not match the version of
add-in?

Both setup.exe and msi can run through regardless the version of Outlook.

MS article "Deploying VSTO 2005 SE Solutions Using Windows Installer"
only talks about VSTO version.