It compares the files on disk and does a bitwise comparison of the files. If they are truly identical, it is smart enough to know. The CompareFiles method is also extensible if you implement a binder extension which would allow you to incorporate any additional smarts that you can infer based on your build environment or source structure.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Sent: Thursday, November 08, 2007 9:55 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] wixpdb When creating patches... Does the wixpdb method compare the binaries from the two .msi files? Or, does it compare the files as they are on the disk? (My preference is for using .msi files due to project archiving and other such things). If it compares the files as they are on the disk, is it wise enough to know when one .msi has a c:\1.0\whatever.exe, and another .msi has c:\1.1\whatever.exe, and the whatever.exe files are exactly identical? ------------------------------------------------------------------------- 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-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- 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-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
