Software Deployment

look at the system requirements page "windows installer runtime version" you can set you installer version to 2.0 and above or as you said 3.0 and above

you will need to make sure you have installed the lastest windows installer engine on your workstation.

That entry determines the minimum version to which your package will deploy. To package for specific versions merely involves using the particular features of that version. For example, one of the differences between v1 and v2 was the ability to digitally sign MSIs.

So, for example, if your package uses a v3-specific feature, set the 'Installer Version' to '3.0'. If it uses v3.1 features, set it to '3.1' and so on.

http://msdn.microsoft.com/en-us/library/aa372796%28VS.85%29.aspx

I did not get your point. I know there are updated Windows Installer versions available. Right now, whatever package [legacy or vendor msi]comes to me I do it. My Windows Installer version is set to 2.
As you are saying as per the package requirement set the installer value. Is it complicated process? How will I get to know, my package is using which Installer version?

My guess:

For legacy application, I can capture it, and create msi which will use version e.g. 3.1
For vendor msi, I will install it on the machine 1st, and if it gives an error for updated Installer version, then I will repackage that msi with updated, Installer version.

Please correct me, if I am wrong!

No. I'm saying that IF your package uses a feature of the WI engine which is specific to, say, v3, then you need to set the 'Installer Version' to 3.0.

Go mad - hit 'F1' when you're in the 'Installation Expert/General Information' view.

I got your point.
CYGAN and VBSCAB thank you for this useful information.