As already mentioned, the developer dashboard is an invaluable tool for the developer who wishes to display information and debug SharePoint code. It is quite extensive too, as it displays information about all the aspects that a developer would wish to track, including SQL calls that are also linked to the entire command line (the one that ran when the call was made). Unfortunately, by default, the Developer Dashboard will not display extensive information about custom code, albeit calls made from within the custom code will be tracked. However, extensive tracking of custom code can be implemented.
The developer can include monitored sections of their custom code to the Developer Dashboard, by implemented the SPMonitoredScope. As best practice, the developer should always wrap any code that executes on SharePoint, within an SPMonitoredScope class. The SPMonitoredScope class is part of the Microsoft.SharePoint.Utilities namespace, so the respective “using” will have to be in place.
The SPMonitoredScope comes with two constructors. The first one, accepts one string that is the name of the new scope. The second one, accepts a string, that is the name of the new scope, an integer that is the maximum time in miliseconds for the execution of the monitored scope and an array of objects that implement the ISPScopedPerformanceMonitor interface. The funny thing is that the SPMonitorScope is said to be unavailable in sandboxed solutions but, according to MSDN, the ISPScopedPerformanceMonitor interface is available in sandboxed solutions (okay, why?). When the maximum time, the integer provided within the constructor, is passed, the frame around the Developer Dashboard turns red and the trace level for the code is increased.
The following table, taken from the invaluable Professional SharePoint 2010 Development by Wrox, displays the classes that implement the ISPScopedPerformanceMonitor interface.
Powered by Zoundry Raven
