Hi Miaohsi, We are currently having a very similar problem where I work. Torch.exe seems to be detecting all of our .NET assemblies as changed, even though only a few of them are actually different in source code. Hence, all of the .NET assemblies are going into the patch, making it is huge and slow to install. We have a theory on what's happening...
In our case, the "new" set of .NET assemblies (the second set that Torch is looking at for comparison) have been re-built and re-signed. Our current theory is that re-signing caused the assemblies to be different on a binary level, and so Torch thinks they changed and needed to be in the MSP. We're in the middle of testing this theory now. If it's the case, I'm going to post a question to this list asking how people usually handle this. Not sure if this helps, but maybe it does :) - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Our-WiX-patch-installer-is-very-slow-tp7217544p7227540.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
