Hi I've been investigating the -cc CAB caching argument to light to speed up some of our developer builds. I'm wondering if there's been a regression?
With the CABs cached, if I make a change that involves re-compiling the MSI but doesn't affect the CABs, such as tweaking a registry key component, light skips the cached CABs and re-links. My understanding of the feature is that it should only rebuild and re-cache the CABs if their specification has changed. I've seen this behavior in the Beta Exit build 4805 (our current "production version") and the RC build 5217 (from private testing). I'm using the <LinkerAdditionalOptions> element in our .wixproj as follows: <LinkerAdditionalOptions>-b $(MsiFilesDir) -cc $(MsiFilesDir)\cab-cache</LinkerAdditionalOptions> where $(MsiFilesDir) is a known location on disk containing the binaries and other files to be stored in the MSI. We're using a number of the WiX extensions, specifically WixNetFxExtension, WixUIExtension and WixUtilExtension. Could these have any bearing on the issue? Many thanks in advance Alastair ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
