MS Test source code view
Eyunni
Posts: 2
Hi,
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:
http://www.red-gate.com/supportcenter/Content?c=knowledgebase/ANTS_Performance_Profiler/KB200708000125.htm&p=ANTS%20Performance%20Profiler
http://www.red-gate.com/supportcenter/Content?c=ANTS_Performance_Profiler/help/6.2/app_mstest.htm&p=ANTS%20Performance%20Profiler
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.
Thanks
Andy
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:
http://www.red-gate.com/supportcenter/Content?c=knowledgebase/ANTS_Performance_Profiler/KB200708000125.htm&p=ANTS%20Performance%20Profiler
http://www.red-gate.com/supportcenter/Content?c=ANTS_Performance_Profiler/help/6.2/app_mstest.htm&p=ANTS%20Performance%20Profiler
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.
Thanks
Andy
Comments
Profiler not finding source code is a common issue, so we have a KB article that may help:
http://www.red-gate.com/supportcenter/C ... 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.