At the time, after researching the the wix source code, I concluded that I could not interact with Engine Variables until after Engine.Detect was called. It may be more relevant that I also concluded that I could not interact with engine variables except in code in a WiX event handler (or code called from those methods. So I added a comment in my App::Run() function to remind me to only interact with Engine objects in the wix event handlers (or in code called by those methods). I just figured that I had originally done something that was not acceptable in a multithreaded environment.
I do not have the specific code that caused the exception, but I can probably recreate the scenario and then file a bug based on that information. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unhandled-exception-when-launching-MBA-tp7598331p7598397.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
