As a follow up to my last email here, it turns out signing was /not/ the issue after all. If we compile a .NET assembly twice in a row (same source code each time) the second DLL is binary-different than the first. Maybe it's putting a time stamp in there. So I'm guessing Torch is doing a binary comparison and seeing all of our assemblies as different each time. I'm going to see if anyone's solved this in this mailing list, and if not I'll ask about it.
- John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Our-WiX-patch-installer-is-very-slow-tp7217544p7227738.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
