Profiling dynamically loaded dlls

Code profiling for .NET developers.

Moderators: AndrewH, melvyn.harbour, james.billings, Laura Morley, dene.boulton

Profiling dynamically loaded dlls

Postby RichardJohnn » Mon May 14, 2012 8:13 pm

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
RichardJohnn
 
Posts: 2
Joined: Mon May 14, 2012 8:10 pm

Postby Brian Donahue » Wed May 16, 2012 9:31 am

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.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Managed DLL

Postby RichardJohnn » Mon May 21, 2012 1:56 pm

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.
RichardJohnn
 
Posts: 2
Joined: Mon May 14, 2012 8:10 pm

Postby Brian Donahue » Mon May 21, 2012 3:30 pm

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.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to ANTS Performance Profiler 7

Who is online

Users browsing this forum: No registered users and 0 guests