[wix-users] Debug Managed Bootstrapper

Mark Olbert Mark at arcabama.com
Thu Jun 8 08:05:24 PDT 2017

Okay, I figured out the problem. Should’ve just searched on the exception code error message.

When you migrate a project to the VS 2017 csproj format, building generates a number of error messages about duplicate attributes in the AssemblyInfo.cs file. I’ve resolved those in other projects by just deleting the AssemblyInfo.cs file (could’ve just commented out the offending lines, but removing the file itself doesn’t seem to cause any problems elsewhere).

But with a bootstrapper app you have to have the assembly: BootstrapperApplication(… attribute.

So deleting AssemblyInfo.cs removes that attribute, causing the problem I encountered.

Too bad the wix loader doesn’t provide a more helpful error message. Is there a away to suggest that the loader scan for the required attribute and, if it’s not found, say something like “No BootstrapperApplication found; have you marked the user interface assembly with…”?

  *   Mark

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: John Cooper<mailto:JoCooper at jackhenry.com>
Sent: Thursday, June 8, 2017 6:17 AM
To: WiX Toolset Users Mailing List<mailto:wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Debug Managed Bootstrapper

Check the Event Viewer.  There's usually an Application Exception and a .NET Framework Exception.  The latter is usually quite helpful.

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 Mark Olbert
Sent: Wednesday, June 7, 2017 11:22 PM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Debug Managed Bootstrapper

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

I have a managed bootstrapper app which was working correctly but is now failing immediately after launch. In other words, everything compiles and builds correctly, but double-clicking the resulting exe file causes a brief screen flicker, and then nothing.

I've checked for log files in user/appdata/local/temp, and there's nothing (there are files from a few days ago, when the exe was working, but nothing more recent).

How do I figure out what's causing the exe to crash immediately upon launch? I've tried waiting for a debugger attachment when my derived BootstrapperApplication class' constructor is called, but that doesn't work.which says this must be a problem very early in the startup.

  *   Mark

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

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/

More information about the wix-users mailing list