Is there a way of informing an end user that a patch is not valid (due to a newer patch all ready being applied)? I currently have a series of MSI files, and a series of patches (MSPs) which progressively upgrade installed instances (say v1.0.1, 1.0.2, and 1.0.3). If I install 1.0.1, and then apply the 1.0.3 MSP, the version upgrades properly, but then I am still allowed to run the 1.0.2 MSP. In the log file I see:
Expected product version == 1.0.1.0, found product version 1.0.3.0. Will not apply because previous transform was invalid.. This tells me attempting to invoke the 1.0.2 MSP is in essence just doing a "repair" of 1.0.3. Since this is maintenance mode, FindRelatedProducts isn't executed. If I use the 1.0.2 MSI file, I get the expected behavior displaying a newer version is already installed message. I am using a validation of 0x00000922 for the transforms. I would have expected identical behavior between the MSI install and the MSP patch. Thanks, Jacob ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
