[wix-users] How to debug into cleanroom installation?

[Jon Earle]

Ah, this helped!  Thanks!


John: What you posted helps when just debugging the .NET code, I wanted to step into the burn.exe to see what was going on.


Thanks guys, I figured out my problem with upgrades and the package and Features not being "seen" (always coming up as Absent): I needed to handle the DetectRelatedMsiPackage event.  I used John Wright's code from here as a basis to get the upgrade sorted out.

http://stackoverflow.com/questions/17552989/how-do-i-detect-the-currently-installed-features-during-a-majorupgrade-using-wix

[http://cdn.sstatic.net/Sites/stackoverflow/img/apple-touch-icon@2.png?v=73d79a89bded&a]<http://stackoverflow.com/questions/17552989/how-do-i-detect-the-currently-installed-features-during-a-majorupgrade-using-wix>

How do I detect the currently installed features during a ...<http://stackoverflow.com/questions/17552989/how-do-i-detect-the-currently-installed-features-during-a-majorupgrade-using-wix>
stackoverflow.com
I'm using WiX 3.7's Burn/Managed Bootstrapper Application features to create a custom MBA-based installer. For each of the packages in my bundle's chain, when ...




Cheers!

Jon

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Sean Hall <r.sean.hall at gmail.com>
Sent: Thursday, September 22, 2016 9:47 PM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] How to debug into cleanroom installation?

To load the BA in the initial process, add the command line

-burn.clean.room="path\to\bundle.exe"

On Thu, Sep 22, 2016 at 3:41 PM, John Cooper <JoCooper at jackhenry.com> wrote:

> There is an early post that has this method.
>
> /// <summary>
>         /// Private method to attach the debugger necessary after <c>WiX
> 3.10.2</c>
>         /// </summary>
>         /// <example>
>         /// 1) Add a line of code early in the mba Run method to call this
> method.
>         /// 2) Compiling the managed <see cref="BootstrapperApplication"/>
> and
>         /// then the bundle.exe, (which is configured in the managed
>         /// <see cref="BootstrapperApplication"/> project as the
> executable to
>         /// load the managed <see cref="BootstrapperApplication"/>
> library), I
>         /// then:
>         /// 3) Open the Solution in another instance of Visual Studio IDE,
> only
>         /// for 'launching' a debug session.  My practice is to close all
>         /// documents in this second IDE instance.
>         /// 4) In the second instance select the managed
>         /// <see cref="BootstrapperApplication"/> project (or set it as
> the
>         /// Startup Project) and hit F5.
>         /// 5) When Attach to Process dialog is presented select the first
>         /// instance of your VS IDE (where you are doing your work).
>         /// </example>
>         [Conditional("DEBUG")]
>         private static void AttachDebugger()
>         {
>             string noDebug = Environment.GetEnvironmentVariable("
> NODEBUG");
>
>             if (string.IsNullOrEmpty(noDebug) || !noDebug.Equals("1"))
>             {
>                 Debugger.Launch();
>             }
>
>             return;
>         }
>
> This method works for me when debugging my MBA.  The NODEBUG was an
> internal requirement, the rest is pretty much as it was originally posted.
>
> --
> John Merryweather Cooper
> Senior Software Engineer -- Integration Development Group -- Enterprise
> Notification Service
> Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Office:
> 913-341-3434x431050
> JoCooper at jackhenry.com
>
>
>
>
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Jon Earle
> Sent: Thursday, September 22, 2016 3:35 PM
> To: 'WiX Toolset Users Mailing List' <wix-users at lists.wixtoolset.org>
> Subject: [wix-users] How to debug into cleanroom installation?
>
> The e-mail below is from an external source.  Please do not open
> attachments or click links from an unknown or suspicious origin.
>
> Following the advice here: http://windows-installer-xml-
> wix-toolset.687559.n2.nabble.com/How-to-debug-Managed-BA-
> Burn-td6630791.html
>
> How to debug Managed BA + Burn - Windows Installer XML ...<
> http://windows-installer-xml-wix-toolset.687559.n2.
> nabble.com/How-to-debug-Managed-BA-Burn-td6630791.html>
> windows-installer-xml-wix-toolset.687559.n2.nabble.com
> How to debug Managed BA + Burn. Here's one way to debug a managed WiX
> Bootstrapper Application (BA) and the Burn engine if you are interested in
> seeing how it works ...
>
>
> I am trying to debug into the burn engine to see why it is not detecting
> my previously installed package properly (always says it's absent).
>
>
> From engine.cpp, line 460:
>
>
> if (!::CreateProcessW(wzCleanRoomBundlePath, sczFullCommandLine, NULL,
> NULL, TRUE, 0, 0, NULL, &si, &pi))
>
>
> It launches the installer again, and I lose my debugging ability after
> that.
>
>
> How can I tell burn to not re-launch the installer into this "clean room",
> or, how can I continue the debug session?
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> NOTICE: This electronic mail message and any files transmitted with it are
> intended
> exclusively for the individual or entity to which it is addressed. The
> message,
> together with any attachment, may contain confidential and/or privileged
> information.
> Any unauthorized review, use, printing, saving, copying, disclosure or
> distribution
> is strictly prohibited. If you have received this message in error, please
> immediately advise the sender by reply email and delete all copies.
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>

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