Jason,
Just a quick follow up... this works exactly as you said :)
So nice to see a stack trace that includes the offending line number as
well.
I'm a huge fan of shipping .PDB's... the exact line number for unexpected
exceptions seems so very useful to me that any associated costs are well
worth the trouble.
Thanks very much!
Rob
ps. I had to upgrade VisualBuildPro from v6 to v7 for this to work (not sure
why but when it was building it would abort with an "null reference" style
of exception). Running msbuild from the command line worked... but for some
reason visualbuildpro just didn't like the .csproj file I guess.
-----Original Message-----
Date: Wed, 8 Jul 2009 18:51:59 -0400
From: "Rob MacFadyen" <rmacfad...@rmtrack.com>
Subject: Re: [WiX-users] WiX-users Digest, Vol 38, Issue 35
To: <wix-users@lists.sourceforge.net>
Message-ID: <103a01ca001e$b4f9f760$1eede6...@com>
Content-Type: text/plain; charset="us-ascii"
Jason,
Thanks a ton! I'll dig into this again and see if I can make it work
(fingers crossed).
Regards,
Rob
-----Original Message-----
Date: Wed, 8 Jul 2009 14:38:38 -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"
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.Mana
gedCA.dll to
C:\temp\CATest\CustomAction1\obj\x86\Debug\Microsoft.Deployment.Samples.Mana
gedCA.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.Mana
gedCA.CA.dll
------------------------------------------------------------------------------
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
