External Method Calls

To make the profiler even more useful, the latest experimental builds now show external calls. External in the case of the profile really means anything not in your solution.

This approach lets you focus on your code, and see at least one more level into referenced libraries as well as the .NET BCL. It keeps performance high by not deeply tracing into assemblies that are part of the framework that you can’t really modify. This is a performance boosting compromise with the goal of letting you pinpoint parts of your code to tune, without cluttering up your view with a lot of .NET framework internal call stacks.

External methods have a little arrow over the icon, and are grayed out indicating they aren’t in your solution …

Remember to get tracing, you’ll need to enable coverage (TestMatrix | Collect Coverage Data)

You can get this feature from the (Experimental) updates starting… now!

  Permalink |  Comments[0]

Recent Entries

 » New Unit Testing Book
 » Build 2293 Update Posted
 » Microsoft Team System NUnit Adapter
 » MS Team System Test Support
 » NUnit 2.4.6 Support

You can leave a response, or trackback from your own site.

Leave a Reply


You must read and type the 5 chars within 0..9 and A..F, and submit the form.


Oh no, I cannot read this. Please, generate a