I am not sure how to reproduce this issue now. I tried what I recalled
running into some months back and did not hit the problem.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unhandled-exception-when-launching-MBA-tp7598331p7598565.html
Sent fr
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 cal
cember-02-14 2:15 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Unhandled exception when launching MBA
>
> I'm not sure if this comment will be much help, but when I started working
> on an mba I made the mistake of trying to interact with Engine Var
Bingo! That did it :) Thank you for the heads up Phill!!!
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: December-02-14 2:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Unhandled exception when launching MBA
I'm not sure if this co
I'm not sure if this comment will be much help, but when I started working on
an mba I made the mistake of trying to interact with Engine Variables early
in my app startup, before DetectBegin handler was fired, which caused
threads to close and then an exception later. I add
System.Diagnostics.Deb
Hey everyone,
Trying to create an MBA based on .NET 4.5. Everything compiled correctly but
when I launch the exe I get an unhandled exception:
"An unhandled Microsoft >NET Framework exception occurred in ExpressMBA.exe
[4400]."
When I attach the VS 2013 debugger the breakpoint is sitting at t
6 matches
Mail list logo