locked
VS11 VSPerfReport PackSymbols RRS feed

  • Question

  • Hi,

    I am using the x64 VS11 Beta profiling tools.

    I ran VSPerfReport /PackSymbols and I've got the following exception:

    Microsoft (R) VSPerf Report Generator, Version 11.0.0.0
    Copyright (C) Microsoft Corporation. All rights reserved.

    Methode nicht gefunden: "Int32 System.Environment.get_CurrentManagedThreadId()".

    Unbehandelte Ausnahme: System.MissingMethodException: Methode nicht gefunden: "Int32 System.Environment.get_CurrentManagedThreadId()".
       bei VSPerfAnalysis.GlobalizedDetoursProcess.<GetDetoursEventStreams>d__0..ctor(Int32 <>1__state)
       bei VSPerfAnalysis.GlobalizedDetoursProcess.get_DetoursStreams()
       bei VSPerfAnalysis.RequestAnalyzer.AnalyzeProcess(DetoursProcess process)
       bei VSPerfAnalysis.RequestAnalyzer.Analyze(IEnumerable`1 processes)
       bei VSPerfAnalysis.DetoursAnalyzer.Analyze(IEnumerable`1 processes)
       bei VSPerfAnalysis.VspDBConnection.AnalyzeDetoursData()
       bei VSPerfAnalysis.VspDBConnection.Open(CancellationToken cancellationToken)
       bei VSPerfPresentation.ProfileDataProvider.OpenFile(String path, OptionStoreoptions, CancellationToken cancellationToken)
       bei Microsoft.VisualStudio.PerformanceTools.CommandLineReport.AnalysisDriver.Open()
       bei Microsoft.VisualStudio.PerformanceTools.CommandLineReport.Report.Main(String[] args)

    How can I workaround it?

    Thanks,


    Martin Kulov
    www.kulov.net

    Microsoft Regional Director
    VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker

    Sunday, March 18, 2012 6:01 PM

Answers

  • The property Environment.CurrentManagedThreadId is a new property of .NET Framework 4.5, so looks like you need to install the .NET Framework 4.5 to get rid of this exception.

    Monday, March 19, 2012 1:54 AM

All replies

  • The property Environment.CurrentManagedThreadId is a new property of .NET Framework 4.5, so looks like you need to install the .NET Framework 4.5 to get rid of this exception.

    Monday, March 19, 2012 1:54 AM
  • More info:

    The machine where the error is generated has VS11 Beta profiling tools installed through the standalone vs_profiler_x64_enu.exe installer. It does not have the full VS11 Beta Ultimate.

    Also the machine has German locale.

    I just tried the PackSymbols command on a machine that has VS11 Beta Ultimate installed with English locale and it works fine.


    Martin Kulov
    www.kulov.net

    Microsoft Regional Director
    VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker

    Monday, March 19, 2012 2:46 AM
  • Thanks Den,

    That's probably the case. 

    However if the profiler has dependency on .NET 4.5 the installer should detect this prerequisite and alert if not found.

    Or better yet just get rid of this method and make the profiler compatible with .NET 4.0.

    Thanks,


    Martin Kulov
    www.kulov.net

    Microsoft Regional Director
    VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker

    Monday, March 19, 2012 2:49 AM
  • You can add your feedbacks in this website.

    Best wishes,


    Mike Zhang[MSFT]
    MSDN Community Support | Feedback to us

    Monday, March 19, 2012 10:18 AM
    Moderator
  • Do you mean the Connect website?

    Or add it here as discussion?

    Thanks!


    Martin Kulov
    www.kulov.net

    Microsoft Regional Director
    VS ALM MVP, MCT, MCSD, MCPD, INETA Speaker

    Monday, March 19, 2012 11:30 AM
  • Yes, it is.

    And sorry for that I forgot the add the link in my pre post: http://connect.microsoft.com/VisualStudio 

    Best wishes,


    Mike Zhang[MSFT]
    MSDN Community Support | Feedback to us

    Tuesday, March 20, 2012 5:14 AM
    Moderator