Re: [WiX-users] Debugging a DTF Managed Custom Action

2008-11-06 Thread Dave Largen
ECTED]@:^[-['^";@@@\\>])@.". "{)/];)^{";$,+=(++$,);$_.=">&$,";`$_`; -Original 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

Re: [WiX-users] Debugging a DTF Managed Custom Action

2008-11-06 Thread Dave Largen
point, 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 process, not the installer process. Chris On Tue, Nov

Re: [WiX-users] Debugging a DTF Managed Custom Action

2008-11-06 Thread Dave Largen
to the CA managed process, not the installer process. Chris On Tue, Nov 4, 2008 at 2:11 PM, Dave Largen <[EMAIL PROTECTED]> wrote: > 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 direc

[WiX-users] Debugging a DTF Managed Custom Action

2008-11-04 Thread Dave Largen
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 ---

Re: [WiX-users] Error 2769: Custom Action Install did not close 1 MSIHANDLEs.

2008-10-28 Thread Dave Largen
always leaks handles. -Original Message- From: Dave Largen [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 11:10 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Error 2769: Custom Action Install did not close 1 MSIHANDLEs. I'm running a WIX install on a Vista box and

[WiX-users] Error 2769: Custom Action Install did not close 1 MSIHANDLEs.

2008-10-28 Thread Dave Largen
I'm running a WIX install on a Vista box and I get the below error when I run a custom action. The action runs fine on an XP box. I am running the installer with elevated privileges from an administrator account. Does anyone have an idea what could be causing this. I am running build 3.0.4624.0