Deploying a Data Processing Extension
Once you have written and compiled your Reporting Services data processing extension into a .NET Framework library, you need to make it discoverable by the report server and by Report Designer. This is as easy as copying the extension to the appropriate directories and adding entries to the appropriate Reporting Services configuration files.
Configuration-File Extension Element
Data processing extensions that you deploy to the report server or Report Designer need to be entered as Extension elements in the configuration files. These files are RSReportServer.config for the report server and RSReportDesigner.config for Report Designer.
The following table describes the attributes for the Extension element for data processing extensions.
|Name||A unique name for the extension, for example, "SQL" for the SQL Server data processing extension or "OLEDB" for the OLE DB data processing extension. The maximum length for the Name attribute is 255 characters. The name must be unique among all entries within the Extensions element of a configuration file.|
|Type||A comma-separated list that includes the fully qualified namespace along with the name of the assembly.|
|Visible||A value of false indicates that the data processing extension should not be visible in user interfaces. If the attribute is not included, the default value is true.|
For more information about the RSReportServer.config or RSReportDesigner.config files, see Reporting Services Configuration Files.
The following table describes the topics in this section.
|Deploying a Data Processing Extension to a Report Server||Describes how to deploy your data processing extension to a report server.|
|Deploying a Data Processing Extension to Report Designer||Describes how to deploy your data processing extension to Report Designer.|