On 20-Jun-12 11:23, David Watson wrote: > after a rebuild some binaries that have unchanged code and version numbers > are not byte by byte identical to the previous version. When I build a test > patch with some of these binaries they are being included in the msp by the > torch auto detection methods (even though they have the same version) but are > obviously are not being installed while patching as the version numbers have > not changed. This is far from ideal as I suspect that most files in our > products would be included in the patch. Probably. Most files end up different in the PE header if nowhere else. Torch uses a binary diff if a file isn't obviously different (i.e., different sizes). Diffing by PE version, if present, seems a fine feature request. It's also something you can do yourself with a BinderFileManager in an extension.
-- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
