I have a WinForms solution with two projects.  I can run the Performance
Explorer in Sampling mode and get reports that list my VB.net methods.  When
I switch to Instrumentation mode the reports contain hex addresses in place
of function names.

I tried deleting the pdb and instr.pdb files but the symptoms did not change.

The output window text is shown below.  Thanks!

Regards,
Tom Allen
Netflix.Com

===============================
Profiler started
Instrumenting C:\Documents and Settings\tallen\My Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\TestDataAccess.exe in
place
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50727 x86
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
  C:\Documents and Settings\tallen\My Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\TestDataAccess.exe -->
C:\Documents and Settings\tallen\My Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\TestDataAccess.exe
Original file backed up to C:\Documents and Settings\tallen\My
Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\TestDataAccess.exe.orig
Successfully instrumented file C:\Documents and Settings\tallen\My
Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\TestDataAccess.exe.
Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit
process.  The CLR header flags have been updated to reflect this.
Instrumenting C:\Documents and Settings\tallen\My Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\UtilityFunctions.dll in
place
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50727 x86
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
  C:\Documents and Settings\tallen\My Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\UtilityFunctions.dll
--> C:\Documents and Settings\tallen\My Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\UtilityFunctions.dll
Original file backed up to C:\Documents and Settings\tallen\My
Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\UtilityFunctions.dll.orig
Successfully instrumented file C:\Documents and Settings\tallen\My
Documents\Visual Studio
2005\Projects\TestDataAccess\TestDataAccess\bin\Debug\UtilityFunctions.dll.
Warning VSP2013 : Instrumenting this image requires it to run as a 32-bit
process.  The CLR header flags have been updated to reflect this.
Successfully attached to process: 5440
Performance automation returned the following error: : Error VSP1386 : 1
buffer(s) lost in association with process 5440
Exited from process: 5440
Collection file exited: C:\Documents and Settings\tallen\My Documents\Visual
Studio 2005\Projects\TestDataAccess\TestDataAccess060307(13).vsp
Profiler exited
Starting analysis for C:\Documents and Settings\tallen\My Documents\Visual
Studio 2005\Projects\TestDataAccess\TestDataAccess060307(13).vsp
Warning VSP2340 : Managed code profiling DLL was not loaded. Environment
variables may not have been set.
Completed Analysis for C:\Documents and Settings\tallen\My Documents\Visual
Studio 2005\Projects\TestDataAccess\TestDataAccess060307(13).vsp
===================== Profiling Complete =====================