Re: [WiX-users] Debugging Managed Bootstrapper Application

2014-03-25 Thread Phill Hogland
In my particular situation the test pc and the dev pc are on different locked down networks so I could not get the remote connection to work. But I hope to solve that issue in the future. -- View this message in context:

Re: [WiX-users] Debugging Managed Bootstrapper Application

2014-03-25 Thread Daniel Madill
Quanser Inc. -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, March 24, 2014 4:04 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Debugging Managed Bootstrapper Application For scenarios that involve running the installer past the detect stage, I

Re: [WiX-users] Debugging Managed Bootstrapper Application

2014-03-25 Thread Adkins, Christopher
To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Debugging Managed Bootstrapper Application I have not been following this thread, but is it not possible to use the Visual Studio Remote Debugging facilities so that you only have to install a bare minimum on the test machine

[WiX-users] Debugging Managed Bootstrapper Application

2014-03-24 Thread gowri.malasani
Hello, how to debug MBA written in C#? I tried this (http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-debug-Managed-BA-Burn-td6630791.html) of course without steps 1 2 as I didn't want to debug engine. But no luck. I just launches the program but it never steps into my

Re: [WiX-users] Debugging Managed Bootstrapper Application

2014-03-24 Thread Tunney, Stephen
System.Diagnostics.Debugger.Launch() at the beginning of your CA will do the job nicely :) -Original Message- From: gowri.malas...@non.agilent.com [mailto:gowri.malas...@non.agilent.com] Sent: March-24-14 3:24 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Debugging

Re: [WiX-users] Debugging Managed Bootstrapper Application

2014-03-24 Thread Phill Hogland
For scenarios that involve running the installer past the detect stage, I moved code to a test box, and I tried to use WinDbg. I installed windbg as the default debugger and got it to attach when the code hits a System.Diagnostics.Debugger.Break(); line in the mba's Run() function, but I did not