I want to debug the problem I'm having with ExePackage/@DetectCondition so I cloned the current git trunk and attempted to run MSBuild on it. I'm new to assembly signing but I think I have my head around the principles from reading a bunch of blogs about it, including the need to use the 64 bit sn.exe on my Vista-64 system.
I run MSBuild from the root of the clone and it fails to run utilities that it builds along the way (like GenerateWixInclude.exe and MakeSfxCA.exe) because they've only been delay-signed. Based on an earlier mailing list entry, I tried pointing envvar OFFICIAL_WIX_BUILD at a temporary public/private key pair but then the project wants a full suite of VS2005/VS2008/VS2010/VS2012 compilers installed, and I only have VS2008 and VS2010. Is there some way to build something I can use to debug with? What's the magic to get the build to run to completion? Is there some way to specify a temporary key pair to get something I can debug with? My objective is to step through condition.cpp to see what it's doing with the variable passed from ComponentSearch to ExePackage. ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
