MS Test source code view

Code profiling for .NET Developers

MS Test source code view

Postby Eyunni » Thu Aug 18, 2011 8:11 pm


I am trying to run some performance tests through Microsoft unit test framework and would like to identify the bottlenecks in the code.

I have gone through these two links below:

After running the unit test, I tried to attach the devenv.exe to the profiler to debug while analyzing the performance. However, what I would like to do is see code-level details. I am not sure if the ANTS profiler is able to identity the pdbs but it cannot find the methods or source code, I dropped the pdbs into devenv.exe container folder but that did not help.

Basically, I need to identify the corresponding source code after profiler summarizes the results.

Posts: 1
Joined: Thu Aug 18, 2011 7:40 pm

Postby Brian Donahue » Fri Aug 19, 2011 8:36 am


Profiler not finding source code is a common issue, so we have a KB article that may help: ... 20Profiler

Generally the rule is to put the PDB in the same folder as the DLL, but there can also be version, timestamp, or build date mismatch between the PDB file and the assembly it documents.
Brian Donahue
Posts: 6590
Joined: Mon Aug 23, 2004 9:48 am

Return to ANTS Performance Profiler Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests