Bugs item #1717526, was opened at 2007-05-11 17:32 Message generated for change (Settings changed) made by pmarcu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1717526&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: pyro Group: v3.0 Status: Open Resolution: None >Priority: 1 Private: No Submitted By: Heath Stewart (heaths) >Assigned to: pmarcu (pmarcu) Summary: New WiX patch build can't build 2.0-style patches Initial Comment: 1. candle fails if the Classification, Manufacturer, etc. properties (non-booleans) aren't authored, but the existence of these attribute values generate an MsiPatchMetadata table which, in some scenarios, makes Windows Installer consider the MSP a 3.0-style patch. 2. patch families may still be interesting with 2.0-style patches because it limits potential regression with obsolescence, yet specifying patch families forces creation of the MsiPatchSequence table, which in most scenarios identifies the patch as a 3.0-style patch. A potential solution would be to pass in patches to obsolesce like //PatchCreation/ReplacePatch and then default to a 2.0-style patch unless now-optional attributes (like PatchFamily/@Version) are specified. Or have an explicit attribute and throw errors accordingly. 3.0-style patches can specify obsolescence in the MSP's Revision Number summary property, but 2.0-style patches cannot have either an MsiPatchMetadata table or MsiPatchSequence table. ---------------------------------------------------------------------- Comment By: Heath Stewart (heaths) Date: 2007-05-24 15:40 Message: Logged In: YES user_id=1335104 Originator: YES Additionally, the Word Count should be modifiable, with perhaps a minimum value of "2" (equates to MSI 2.0 or higher is required). This, unlike other similar fields, is a lookup table - not the typical "major * 100 + minor" format. This should not dictate the creation of the MsiPatch* tables in the MSP, however. It is perfectly reasonable to require a minimum of MSI 2.0 to install the patch, but support MSI 3.0+ features. .NET 2.0 patches from Microsoft currently are authored this way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1717526&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
