[wix-users] Debugging managed BA

[Goran Malovic]

Hi Phill,
I am not quite sure where to put this switch. Here is how my scenario looks like:
I have MyProject.Bootstrapper and MyProject.Bootstrapper.UI projects. In the properties of MyProject.BootStrapper.UI I, under the Debug option I have set Start action to Start external program and pointed to E:\My Solution\MyProject.Bootstrapper\bin\Debug\ApplicationName.exe
I have tried pasting below switch into command line arguments of the Bootstrapper.UI, but that did not help.
-burn.clean.room="E:\My Solution\MyProject.Bootstrapper\bin\Debug\ApplicationName.exe"
I did not have to provide any pdbs previously, since I did not require the option to debug through the burn code.
Where exactly should I add the switch you are talking about? 
 

On Monday, December 5, 2016, 3:29:47 PM GMT+1, Phill Hogland <phill.hogland at rimage.com> wrote:When you say that debugging used to work about a year ago and now you cannot debug, I think you are referring to the 'breaking change' which was documented in the 10.3.2

http://lists.wixtoolset.org/pipermail/wix-users-wixtoolset.org/2016-January/001251.html


There are several possible solutions, but I think the preferred solution is that when you want to debug, add the following switch to your bundle (or rather to your 'start external program' settings for your mba.dll project).

-burn.clean.room=<path to the external bundle to debug your mba>\bundle.exe


With this change you do not need to make any other changes to your bundle authoring or to the approach used to debug your mba.  Presumably if you were able to debug previously you already had VS configured to find the pdbs, etc, otherwise the steps you did previously to configure VS are still relevant.

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Goran Malovic <malovicg at yahoo.com>
Sent: Saturday, December 3, 2016 11:07:26 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Debugging managed BA

Hi,
I have a problem with debugging managed BA. It used to work without problems, but i haven't been using it for the last year, and don't know when it was broken.
So, I have been using suggestion from Rob on SO, and that stopped working. I have ensured that all is built, I run the app, I place breakpoint on BootstrapperApplication.Run() method (and on lots of other different places), but it is not hit. However, the placed breakpoint itself is red, so it is givining an impression that it is "active and loaded". After the F5 Setup.exe is started and shown on screen, which is correct, but I cannot step through the managed BA code.
My BA is built on .NET framework 3.5 Client Profile. I am using VS 2015, and Wix 3.10.3 Here is BootstrapperCore.config:
  <configSections>
    <sectionGroup name="wix.bootstrapper" type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup, BootstrapperCore">
      <section name="host" type="Microsoft.Tools.WindowsInstallerXml.Bootstrapper.HostSection, BootstrapperCore" />
    </sectionGroup>
  </configSections>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v2.0.50727" />
    <supportedRuntime version="v4.0" />
  </startup>
  <wix.bootstrapper>
    <host assemblyName="Project.Bootstrapper.UI">
      <supportedFramework version="v3.5" />
      <supportedFramework version="v4\Client" />
      <supportedFramework version="v4\Full" />
    </host>
  </wix.bootstrapper>
</configuration>
Any ideas?
Thanks,Goran




____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/