| title | Custom report item implementation requirements | |
|---|---|---|
| description | Learn about the development and deployment requirements that you need for custom report item implementations. | |
| ms.date | 09/25/2024 | |
| ms.service | reporting-services | |
| ms.subservice | custom-report-items | |
| ms.topic | reference | |
| ms.custom |
|
|
| helpviewer_keywords |
|
This article discusses the prerequisites for developing and deploying custom report items.
Developing a custom report item for [!INCLUDEssRSnoversion] requires the following criteria:
-
Administrative access to a server running [!INCLUDEmsCoName] [!INCLUDEssNoVersion] with [!INCLUDEssRSnoversion] and [!INCLUDEssBIDevStudioFull].
-
[!INCLUDEmsCoName] [!INCLUDEvsprvs2005] or newer with the [!INCLUDEmsCoName] [!INCLUDEdnprdnshort] software development kit (SDK) installed.
-
Access to the [!INCLUDEdnprdnshort] SDK documentation.
-
Familiarity with component authoring and the component model namespaces in [!INCLUDEvsprvs].
[!INCLUDEssNoVersion] custom report items fully support the [!INCLUDEdnprdnshort]. You can develop custom report items using your choice of .NET-compliant languages.
[!INCLUDEvsprvs] offers the developer many tools and features to simplify and accelerate the iterative cycles of coding, debugging, and testing and to make deployment easier. The [!INCLUDEdnprdnshort] SDK includes [!INCLUDEvisual-basic] and C# compilers and related tools.
-
Custom report items use the Microsoft.ReportDesigner and xref:Microsoft.ReportingServices.Interfaces namespaces. These are stored in the Microsoft.ReportingServices.Designer.DLL and Microsoft.ReportingServices.Interfaces.DLL assemblies, which are installed as part of [!INCLUDEssRSnoversion].
-
Custom report item design-time components need to implement interfaces from the xref:System.ComponentModel namespace in the [!INCLUDEdnprdnshort]. The xref:System.ComponentModel is documented in the [!INCLUDEdnprdnshort] SDK documentation.