Or one could disable optimization in the Release build. We do this frequently so that we can debug released code at a user's site using WinDbg (with Release build dependencies). I am familiar with the effects of optimization on debugging code. I also had my in-house WinDbg expert double check my observations before raising any comment in the forum. This just did not appear to be an optimization issue, as the path took a different execution route than I had expected and ProcessMon showed issue with loading the theme resources. I still hope to be able to get to the point where I can build the Wix Toolset and remove any question of the test process. I appreciate your time and the feedback. Phill
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdBA-LoadBootstrapperBA-changes-m-fPrereq-tp7588034p7588146.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
