Schmitz, John wrote: > For various reasons, our product setups are built using a number of merge > modules that package our own build products. This, along with my not thinking > about the consequences, resulted in my previous attempts violating at least 3 > of the rules that MS documents governing proper patch builds (ref > http://msdn.microsoft.com/en-us/library/aa368060(VS.85).aspx). Specifically, > the file sequences were changing because files were added in the middle of > the sequence, and files were deleted. Also the order the merge modules were > referenced was inadvertently changed, which ends up changing the file > sequence. All of these errors resulting in MSIMSP incorrectly believing that > almost all the files had been ADDED as a part of the patch. >
That's an excellent example of why WiX supports .wixlibs (instead of merge modules) and patching (instead of msimsp/patchwiz). -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
