Instrumenting Excel 2007 VSTO add-in using Visual Studio 2010 Performance Explorer

Blocat Instrumenting Excel 2007 VSTO add-in using Visual Studio 2010 Performance Explorer

  • Thursday, June 28, 2012 3:28 PM
     
     

    Hi,

    I am trying to instrument my Excel 2007 VSTO add-in using VS2010 Performance explorer. 

    In the performance explorer wizard dialog "Choose the modules to profile using the instrumentation method", if I select my project (ExcelAddIn2) and start profiling, the add-in seems to run normally, but when it stops, it do not receive any output. Output in Performance window is below:

    Profiling started.
    Instrumenting C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\obj\Debug\ExcelAddIn2.dll in place
    Info VSP3049: Small functions will be excluded from instrumentation.
    Microsoft (R) VSInstr Post-Link Instrumentation 10.0.30319 x86
    Copyright (C) Microsoft Corp. All rights reserved.
    File to Process:
       C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\obj\Debug\ExcelAddIn2.dll --> C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\obj\Debug\ExcelAddIn2.dll
    Original file backed up to C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\obj\Debug\ExcelAddIn2.dll.orig
    Successfully instrumented file C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\obj\Debug\ExcelAddIn2.dll.
    Data written to C:\Users\atipatr\Dev\Test\ExcelAddIn2\excel120628(9).vsp.
    Profiling finished.
    File contains no data buffers
    File contains no data buffers
    Analysis failed
    Profiling complete. 

    On the other hand, if I select the DLL option, specify the DLL location (in bin\Debug) and locations to my Excel.exe as executable, and start profiling, the add-in also seems to run normally, and the profiler produces some output. However, all I am getting are addresses (e.g 0x06000035), rather than function names. Output from performance windows follows:

    Instrumenting C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\bin\Debug\ExcelAddIn2.dll in place
    Info VSP3049: Small functions will be excluded from instrumentation.
    Microsoft (R) VSInstr Post-Link Instrumentation 10.0.30319 x86
    Copyright (C) Microsoft Corp. All rights reserved.
    File to Process:
       C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\bin\Debug\ExcelAddIn2.dll --> C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\bin\Debug\ExcelAddIn2.dll
    Original file backed up to C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\bin\Debug\ExcelAddIn2.dll.orig
    Successfully instrumented file C:\Users\atipatr\Dev\Test\ExcelAddIn2\ExcelAddIn2\bin\Debug\ExcelAddIn2.dll.
    Profiling process ID 3056 (EXCEL).
    Process ID 3056 has exited.
    Data written to C:\Users\atipatr\Dev\Test\ExcelAddIn2\EXCEL120628(10).vsp.
    Profiling finished.
    Error VSP1701: Failed to open image C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\sorttbls.nlp (image ID 0).
    Error VSP1701: Failed to open image C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\sortkey.nlp (image ID 0).
    Profiling complete.

    Any help is apperciated.

    Thanks,

    dak

All Replies

  • Monday, July 02, 2012 5:30 AM
    Moderator
     
     Answered

    Hi dak,

    Thank you for posting in the MSDN forum.

    Profiling finished.

     Error VSP1701: Failed to open image C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\sorttbls.nlp (image ID 0).

     Error VSP1701: Failed to open image C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\sortkey.nlp (image ID 0).

     Profiling complete.

    Since you using the Excel VSTO add-in, and based on the error messages, like this thread “Fatal errors during concurency visualisation analysis”, I’m afraid that it is hard for us to repro this issue, to help you resolve this issue as soon as possible, you could submit this feedback to Microsoft Connect feedback portal: http://connect.microsoft.com, Microsoft engineers will evaluate them seriously. Thanks for your understanding. If this issue is urgent, please contact support at http://support.microsoft.com. If you subbmit a feedback, I hope you could share us the link, I will vote it. Thanks for your understanding again.

    Sincerely,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us