Updated documentation to say this is disabled by default since it doesn't always work correctly.
2012-05-25 13:18:05 PDT in Windows Installer...
Thanks, we'll continue it over on the list.
2012-05-25 00:12:51 PDT in Windows Installer...
Discussed in triage. Please continue over email on wix-users@lists.sourceforge.net if the informatin below (including links to documentation stating this) isn't enough. If the WinSDK tools work that way, either there's a documentation bug (and we implement the documentation) or the tools have a bug. The 4th field (which is all you're changing) has never been targetable since MSI 1.0 with...
2012-05-24 20:23:48 PDT in Windows Installer...
I would like to also see your PCP file (or PatchCreation file for WiX). PatchWiz/msimsp won't build a patch with a mix of small update and minor upgrade transforms so it appears something else may be happening in your repro.
2012-05-22 21:44:28 PDT in Windows Installer...
I should also note that even if you add a PropertyRef to the ProductVersion property in Patch.wxs (as a patch family, which pulls in changes to the ProductVersion) - it still doesn't matter since Windows Installer doesn't care about the 4th digit of ProductVersion. For example, patch v1.0.1.3 against product v1.0.1.2 still uses transform T1 and things it's a "QFE" transform, which...
2012-05-22 18:56:21 PDT in Windows Installer...
I should also note I can't access your MSP. I'm getting a 404. We also use multi-targeting for .NET and have for VS, so I know it works. For example, in the attached projects I have patch v1.0.1.3 targeting v1.0.1.1 and v1.0.1.2. Only changes to a registry-only component are taken in. In debug logs for both installs, you'll see: MSI (s) (84:84) [18:38:32:087]: PATCH SEQUENCER...
2012-05-22 18:45:40 PDT in Windows Installer...
That's what I'm trying to tell you and is stated clearly in the Windows Installer SDK: changing just the 4th field of ProductVersion IS NOT a minor upgrade. Windows Installer does not - and never has - targetted the 4th field. So if you have separate transforms that target 1.0.1.1 and 1.0.1.2 but the transforms that target 1.0.1.2 are enumerated first, that explains the behavior you're seeing...
2012-05-22 16:22:47 PDT in Windows Installer...
The documentation is clear. If the SDK is generating and attaching transforms in the order you expect that would explain the observed behavior. The first matching transforms (the order is actually undocumented, but should be deterministic) are used and any others are ignored. But Windows Installer does not and never has used the 4th field of the ProductVersion. If you feel the Windows...
2012-05-21 15:57:22 PDT in Windows Installer...
The SDK tools must be putting the transforms in a different order, so you're only getting "lucky". The Windows Installer documentation is quite explicit: From http://msdn.microsoft.com/en-us/library/windows/desktop/aa370859(v=vs.85).aspx, "Note that Windows Installer uses only the first three fields of the product version. If you include a fourth field in your product...
2012-05-18 12:52:29 PDT in Windows Installer...
See the documentation for light (light.exe) in wix.chm for details.
2012-05-18 12:46:13 PDT in Windows Installer...