Profiling dynamically loaded dlls

RichardJohnnRichardJohnn Posts: 3
edited May 21, 2012 10:30AM in ANTS Performance Profiler Previous Versions
Are there any special tips for profiling a .NET DLL that is loaded at run time? The profiler seems to think it is managed code and when it decompiles it just shows the thread.start()

Thank you
· Share on Twitter

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hi Richard,

    Just to clarify, you do not profile a DLL, you profile the process. If your process loads the DLL and it is managed code, you should get results for it.

    Is this a question about the integrated "Reflector" decompilation? Is the DLL not managed? In other words do you see profiling results and just do not get results from decompilation?

    Please let us know what the problem is.
    · Share on Twitter
  • RichardJohnnRichardJohnn Posts: 3
    Ah ok, thank you.

    The DLL is a managed .NET DLL, but all I see is a call to managed code, there are no details, so maybe it is an issue with the decompilation.
    · Share on Twitter
  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    If you have the filters set correctly (all methods, all threads, not hiding insignificant methods) then all managed methods should appear in the tree view regardless of whether decompilation is possible.

    Decompilation just refers to the source code window.
    · Share on Twitter
Sign In or Register to comment.