Debugging Delivery Extension Code
The Microsoft .NET Framework provides several debugging tools that can help you analyze your delivery extension code and locate errors in it. The tool that works best will depend on what you are trying to accomplish. This example uses Microsoft Visual Studio 2005.
To debug your delivery extension code
Launch Visual Studio 2005 and open your delivery extension project.
Build the project and deploy your delivery extension assembly and the accompanying .pdb file to the report server and Report Manager. For more information about deployment, see Deploying a Delivery Extension.
If you have written a subscription user interface to extend Report Manager, open Internet Explorer and navigate to Report Manager while leaving your delivery extension code open in Visual Studio. If you do not have a subscription user interface deployed for Report Manager, simply open the client application from which you call your delivery extension using the SOAP API.
Navigate to Visual Studio and your delivery extension project, and set some break points in your code.
With the delivery extension project still the active window, click Process on the Debug menu.
The Processes dialog opens.
From the list of processes, select the aspnet_wp.exe process (or w3wp.exe if your application is deployed on IIS 6.0), and click Attach. When the Attach to Process dialog opens, make sure that the program type Common Language Runtime is selected, and then click OK.
Define a new subscription using your delivery extension. You will most likely use Report Manager or the SOAP API. This should invoke the debugger and execute code corresponding to your break points.
Step through your code using the F11 key. For more information about using Visual Studio for debugging, see your Visual Studio documentation.
See Also
Reference
Reporting Services Extension Library
Other Resources
Implementing a Delivery Extension