Just tried again and it does work -- I got line numbers in the stack trace in 
the log.

Note if you're referencing $(IntermediateOutputPath) like in my example below, 
you need to define the CustomActionContents property at the BOTTOM of your 
project file, because $(IntermediateOutputPath) isn't created until 
Microsoft.Common.targets is included.

At runtime the entire CA package is always extracted. At build time you should 
be able to see the PDB getting included in the CA package in the MSBuild 
output/log, it looks like this:

Modifying SfxCA.dll stub
Copying file version info from 
C:\temp\CATest\CustomAction1\obj\x86\Debug\Microsoft.Deployment.Samples.ManagedCA.dll
 to 
C:\temp\CATest\CustomAction1\obj\x86\Debug\Microsoft.Deployment.Samples.ManagedCA.CA.dll
Packaging files
    Microsoft.Deployment.Samples.ManagedCA.dll
    Microsoft.Deployment.WindowsInstaller.dll
    CustomAction.config
    Microsoft.Deployment.Samples.ManagedCA.pdb
MakeSfxCA finished: 
C:\temp\CATest\CustomAction1\obj\x86\Debug\Microsoft.Deployment.Samples.ManagedCA.CA.dll


-----Original Message-----
From: Rob MacFadyen [mailto:rmacfad...@rmtrack.com] 
Sent: Wednesday, July 08, 2009 1:49 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] DTF and PDB files for better error logging

Jason,

I did this at one point but it was ineffective. On the installation side it
appeared that the .PDB was not being extracted to the temporary directory.

Are you certain this actually works and results in line numbers showing in
stack traces for unhandled exceptions in managed CA's?

Thanks,

Rob

-----Original Message-----

Date: Wed, 8 Jul 2009 12:32:07 -0700
From: Jason Ginchereau <jason...@microsoft.com>
Subject: Re: [WiX-users] DTF and PDB files for better error logging
To: "wix-users@lists.sourceforge.net"
        <wix-users@lists.sourceforge.net>
Message-ID:
        
<139942f2536b7c4fbde6b44132f80c842c4cd76...@na-exmsg-c111.redmond.corp.micro
soft.com>
        
Content-Type: text/plain; charset="us-ascii"

You can add additional items to the CA package by manually adding a
CustomActionContents property to your project file. For example, to include
your assembly PDB when building in debug mode:

<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x86' ">
<CustomActionContents>$(IntermediateOutputPath)$(AssemblyName).pdb</CustomActionContents>
</PropertyGroup>



------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to