| title | Referencing Assemblies in an RDL File | Microsoft Docs | |||||
|---|---|---|---|---|---|---|
| ms.custom | ||||||
| ms.date | 03/06/2017 | |||||
| ms.prod | sql-server-2014 | |||||
| ms.reviewer | ||||||
| ms.technology | reporting-services | |||||
| ms.topic | reference | |||||
| helpviewer_keywords |
|
|||||
| ms.assetid | 9a48e552-7d47-4243-9be1-894990c506d9 | |||||
| author | maggiesMSFT | |||||
| ms.author | maggies | |||||
| manager | kfile |
To support the use of custom code assemblies in report definition files, two Report Definition Language (RDL) elements are included in the RDL specification: the CodeModules element and the Classes element.
The CodeModules element enables you to refer to managed code assemblies in report expressions. CodeModules is a top-level element that contains the reference to the assembly that you use in your report definition files to call specialized functions. An entry in a report definition that supports the use of a custom assembly might look like the following:
<CodeModules>
<CodeModule>CurrencyConversion, Version=1.0.1363.31103, Culture=neutral, PublicKeyToken=null</CodeModule>
</CodeModules>
Instead of calling xref:System.Reflection.Assembly.Load%2A from your custom code, register your custom assemblies by either manually adding CodeModule elements to your RDL file or by using the References tab of the Report Properties dialog. For more information, see Custom Code and Assembly References in Expressions in Report Designer (SSRS).
The Classes element supports the use of instance members in a report definition. Classes is a top-level element that contains a reference to the class name and an instance name. An entry in a report definition that supports the use of instance members might look like the following:
<Classes>
<Class>
<ClassName>CurrencyConversion.DollarCurrencyConversion</ClassName>
<InstanceName>m_myDollarConversion</InstanceName>
</Class>
</Classes>
For more information, see Accessing Custom Assemblies Through Expressions.