Microsoft KB Archive/842855

= Documentation errors and corrections in Reporting Services Books Online topics about debugging and deploying custom assemblies and report server extensions =

Article ID: 842855

Article Last Modified on 4/3/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Reporting Services

-



INTRODUCTION
In Reporting Services Books Online January 2004 Update, the following topics contain documentation errors:
 * &quot;Debugging Custom Assemblies&quot;
 * &quot;Debugging Data Processing Extension Code&quot;
 * &quot;Debugging Delivery Extension Code&quot;
 * &quot;Deploying the Printer Delivery Sample&quot;
 * &quot;Deploying FsiDataExtension&quot;

This article describes the correct information for each of these topics. This article also describes additional information about adding new CodeGroup elements that grant permissions to the custom assemblies or to the report server extensions in the policy configuration files.



MORE INFORMATION
The following topics in Reporting Services Books Online January 2004 Update include information about debugging custom assemblies and custom report server extensions:
 * &quot;Debugging Custom Assemblies&quot;
 * &quot;Debugging Data Processing Extension Code&quot;
 * &quot;Debugging Delivery Extension Code&quot;

These topics tell you to make sure that the Common Language Runtime program type and the Native program types are selected in the Attach to Process dialog box when you debug custom assemblies or custom report server extensions. However, if you select the Native program type in the Attach to Process dialog box, the debugging performance of Microsoft Visual Studio .NET 2003 decreases. Therefore, click to select only the Common Language Runtime program type to debug the custom assemblies and the custom report server extensions.

The following list describes the documentation errors and the corrections for each topic:
 * Step 6 in the &quot;To debug using two instances of Visual Studio&quot; section in the &quot;Debugging Custom Assemblies&quot; topic contains the following information:

&quot;From the list of processes, select the devenv.exe process that corresponds to your Report Project and click Attach. When the Attach to Process dialog opens, make sure that the program types Common Language Runtime and Native are selected, and then click OK.&quot;

The step should read as follows:

&quot;From the list of processes, select the evenv.exe process that corresponds to your Report Project, and then click Attach. When the Attach to Process dialog opens, make sure that the Common Language Runtime program type is selected, and then click OK.&quot;
 * Step 6 in the &quot;To debug your data processing extension code&quot; section in the &quot;Debugging Data Processing Extension Code&quot; topic contains the following information:

&quot;From the list of processes, select the devenv.exe process that corresponds to your Report Project and click Attach. When the Attach to Process dialog opens, make sure that the program types Common Language Runtime and Native are selected, and then click OK.&quot;

The step should read as follows:

&quot;From the list of processes, select the devenv.exe process that corresponds to your Report Project, and then click Attach. When the Attach to Process dialog opens, make sure that the Common Language Runtime program type is selected, and then click OK.&quot;
 * Step 6 in the &quot;To debug your delivery extension code&quot; section in the &quot;Debugging Delivery Extension Code&quot; topic contains the following information:

&quot;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 types Common Language Runtime and Native are selected, and then click OK.&quot;

The step should read as follows:

&quot;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 Common Language Runtime program type is selected, and then click OK.&quot;

Additionally, Reporting Services Books Online January 2004 Update contains errors in the &quot;Deploying the Printer Delivery Sample&quot; topic and in the &quot;Deploying FsiDataExtension&quot; topic.

Deploying the Printer Delivery Sample
In the &quot;Build Location&quot; section of this topic, step 5 in the &quot;To compile the sample using Visual Studio .NET&quot; procedure contains the following information:

&quot;Click Browse, and find the Microsoft.ReportingServices.Interfaces on your local drive. By default, the assembly is located in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin, then click OK.&quot;

The step should read as follows:

&quot;Click Browse, and find the Microsoft.ReportingServices.Interfaces.dll on your local drive. By default, the assembly is located in C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin, then click OK.&quot;

Deploying FsiDataExtension
In the &quot;Deployment&quot; section of this topic, step 3 in the &quot;To configure code access security for the sample&quot; procedure contains code group information that mentions the path of the Microsoft.Samples.ReportingServices.FsiDataExtension.dll assembly that is deployed in Report Designer. The path is not correct:    The code group information should read as follows:   

New CodeGroup elements in the policy configuration files of Reporting Services
After you create a custom assembly or a custom report server extension, you must add a code group if you have to increase code permissions beyond the default execution permissions. You must modify the Reporting Services security policy configuration files, such as the report server policy configuration file Rssrvpolicy.config, to add the code group.

The order of the code groups in the policy configuration files is important. Therefore, we recommend that you add the code groups that correspond to your custom assembly or to the custom report server extension immediately after the existing code group entry that has the URL membership condition set to &quot;$CodeGen$/*&quot;. For example, you can add a code group for your custom assembly or for the custom report server extension in a policy configuration file as follows:      

