I've attempted to fix a bug mentioned by Rob about ExitCode in Burn (actually candle) as it's pretty urgent for me to have that working for my project. I thought I may be able to just copy over the modified candle.exe and wix.dll into my Program Files (x86)\Windows Installer XML v3.6 directory. But of course, I am getting an exception, not able to load wix.dll with PublicKey=blahblahblah. File not found.
Of course, my modified wix.dll has a null public key. I've made several attempts to work around this, but all unsuccessful. So... what is the recommended way of running a built version of WiX? Could anyone offer any suggestions to get me on the fast track? Can you think of any "quick and dirty" shortcuts I could take to just get my modified candle.exe running? My only change was to add a few items to wix.xsd. I built with "make ship". It doesn't compile completely. I get 8 non-fatal errors and 3 warnings, but I don't even have Visual Studio 2005 installed, so I'm guessing that could be the 2005 Votive components? I do have Visual Studio SDK for 2010, and should also have HTML Help SDK. I do also see an error from "make ship" about can't find "wix\build\ship\x86\Dependency.wixlib". Any help or ideas would be very much appreciated. Thanks, Dan ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
