I'm testing my MBA on various versions of windows server, and on 2003R2x64,
my installer just dies silently. Below are the contents of the logfile:
[0458:0820][2013-11-07T11:11:11]i001: Burn v3.7.1224.0, Windows v5.2 (Build
3790: Service Pack 2), path: C:\Documents and
Some things to try:
* Is the MSI failing? There ought to be separate MSI log files in the same
directory, so check those for any errors.
* Check the bootstrapper's log file to see how far it gets, may give you a
clue about where it's failing
* If you want to step into your managed BA, put a
I like to use the AssertSz(FALSE, debug XxxCA here); from dutil.h. The
resulting dialog gives lots of information to make it easy to attach.
On Wed, Aug 25, 2010 at 2:00 PM, gapearce mr_gapea...@yahoo.com wrote:
I found it pretty easy and straightforward using VS2008 to attach to a
setup
Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Tuesday, August 24, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL
Dear Wix Experts:
We have a CustomAction DLL written in C. How to debug it?
There are a few posts about
-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Tuesday, August 24, 2010 5:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug CustomAction DLL
I think I recall you sometimes have to reboot and/or restart the Msiexec
I found it pretty easy and straightforward using VS2008 to attach to a setup
program awaiting user input from a message box. It was very easy...
This MSND article touches on it -
http://msdn.microsoft.com/en-us/library/aa368264%28VS.85%29.aspx -
just attach to the process that has your
Dear Wix Experts:
We have a CustomAction DLL written in C. How to debug it?
There are a few posts about it:
Post1:
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom-action/
Post2: http://blogs.msdn.com/b/astebner/archive/2005/06/17/430320.aspx
Post3:
, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL
Dear Wix Experts:
We have a CustomAction DLL written in C. How to debug it?
There are a few posts about it:
Post1:
http://www.davidmoore.info/2010/06/28/how-to-debug-a-windows-installer-custom
...@ymail.com]
Sent: Tuesday, August 24, 2010 5:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug CustomAction DLL
Dear Wix Experts:
We have a CustomAction DLL written in C. How to debug it?
There are a few posts about it:
Post1:
http://www.davidmoore.info/2010/06/28/how
-
From: Tom Crozier [mailto:tcroz...@rackwise.com]
Sent: Wednesday, November 18, 2009 8:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug upgrade problem
I didn't see it before but
FindRelatedProducts: current install is per-user. Related install
+us...@instyler.com]
Sent: Wednesday, November 18, 2009 12:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to debug upgrade problem
Doesn't the msi verbose log say anything?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast
I created an installer that contains 2 Upgrade sections for 2 different
products that are installed however when I run the installer it only locates
one of them. How do I go about debugging this to find out why the 2nd is not
detected by FindRelatedProducts? I did a small test app and this
Doesn't the msi verbose log say anything?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On 17.11.2009, at 22:55, Tom Crozier wrote:
I created an installer that
Our kit has a feature that's depending on
VS90_IDE_VC_PROJECTSYSTEM_INSTALLED being defined. I'm installing onto a
VMWare image with VS2008 and (only) Visual C++ installed, and the feature
fails to install. The feature that depends on VS2005 seems to install
properly onto a similarly configured
Verbose log file gives you that and with recent Windows Installers (v3+?) it'll
even show you when properties change value.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 30, 2008 13:43
To: wix-users@lists.sourceforge.net
Subject: [WiX-users
In article [EMAIL PROTECTED],
Rob Mensching [EMAIL PROTECTED] writes:
Verbose log file gives you that and with recent Windows Installers
(v3+?) it' ll even show you when properties change value.
A trick I've employed is to add a debug dialog to the UI. Setting a
property from the
I fixed the problem by adding the dll entry method name in a .def file for
the project.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No
*Subject:* RE: [WiX-users] How to debug a CustomAction 1723 error ondll
invocation?
Yes. The dll that is invoked is installed by the installer. Given that,
can you advise what would be the proper point in the install execute
sequence to call the action?
Thanks-
Carter
Hi-
I have a custom action I execute on uninstall, and it fails popping a
dialog saying A DLL required for this install to complete could not be run
(from msiexec log)-
MSI (s) (F8:18) [15:35:49:202]: Creating MSIHANDLE (2) of type 790542 for
thread 1560
MSI (s) (F8:2C) [15:35:49:202]: Invoking
Does your CustomAction have dependencies on the machine that get removed during
uninstall?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carter Sanders
Sent: Tuesday, July 03, 2007 12:25 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to debug a CustomAction 1723
20 matches
Mail list logo
