Excellent! Thanks for the info.
Dave
-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 4:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
What I did when
: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 05, 2008 4:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
What I did when debugging some of my DTF code was put a call to
Debugger.Launch() right
[mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 8:51 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
I just tried both techniques the one Chris mentioned is how I've always
debugged my managed custom actions
.
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
That might be a problem with symbols. Did you keep your DLLs and PDB files
in their original locations after you built them?
##
$_='^#(/||/@[EMAIL PROTECTED
.'
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
I keep the .dll and pdb files in the same location but there is no pdb for
the .dll generated from MakeSFXCA application.
-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 12
Message-
From: Dave Largen [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 8:51 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
I just tried both techniques the one Chris mentioned is how I've always
]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;
-Original Message-
From: Christopher Karper [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 04, 2008 6:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Debugging a DTF Managed Custom Action
There is a way using
Is there any way to step into a managed DTF Custom Action with a visual
studio debugger? With regular managed custom actions I can attach directly
to the process running the custom action and step through the code.
Thanks,
Dave
There is a way using Environment variables to set a breakpoint, but I've
found that to be more trouble than it's worth. You can put a call at the
beginning of your CA to MessageBox.Show, and then when that pops up, you can
attach to the process then. Make sure you attach to the CA managed
9 matches
Mail list logo
