Update extending-report-designer.md (#1530)
* Update extending-report-designer.md * Update extending-report-designer.md --------- Co-authored-by: Todor Arabadzhiev <todor.arabadzhiev@progress.com>
This commit is contained in:
Dimitar Nikolov
GitHub
Родитель
3eec817831
Коммит
f786eff9de
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Extending Report Designer
|
||||
page_title: Extending Report Designer at a Glance
|
||||
description: Learn how to make the Telerik Reporting Standalone Designer recognize custom CLR public methods and properties to be used as User functions and ObjectDataSources.
|
||||
description: "Learn how to make the Telerik Reporting Standalone Designer recognize custom CLR public methods and properties to be used as User functions and ObjectDataSources."
|
||||
slug: telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/extending-report-designer
|
||||
tags: extending,report,designer
|
||||
published: True
|
||||
|
|
@ -11,9 +11,9 @@ previous_url: /standalone-report-designer-extending-configuration
|
|||
|
||||
# Extending Report Designer to Recognize Custom Assemblies
|
||||
|
||||
It is a common requirement to add your own [User Functions]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions%}) or bind to custom CLR objects, data models (such as an Telerik Data Access model), external assemblies with custom data source objects, data feeds (including OData), and web services.
|
||||
It is a common requirement to add your own [User Functions]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions%}) or bind to custom CLR objects, data models (such as a Telerik Data Access model), external assemblies with custom data source objects, data feeds (including OData), and web services.
|
||||
|
||||
In order to expose your data, so it can be utilized by the Object/OpenAccess/Entity [data source components]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}), or extend the default behavior of the Telerik Reporting engine with custom User Functions, you have to use the [assemblyReferences Element]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/assemblyreferences-element%}) of the Telerik.Reporting configuration section to reference your custom assembly:
|
||||
To expose your data, so it can be utilized by the Object/OpenAccess/Entity [data source components]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}), or extend the default behavior of the Telerik Reporting engine with custom User Functions, you have to use the [assemblyReferences Element]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/assemblyreferences-element%}) of the Telerik.Reporting configuration section to reference your custom assembly:
|
||||
|
||||
````XML
|
||||
<configuration>
|
||||
|
|
@ -32,31 +32,32 @@ In order to expose your data, so it can be utilized by the Object/OpenAccess/Ent
|
|||
</Telerik.Reporting>
|
||||
</configuration>
|
||||
````
|
||||
|
||||
This can be achieved either by manually editing the configuration file or by using the Standalone Report Designer's **Options** page.
|
||||
|
||||
## Update the Designer Configuration File Throught the UI
|
||||
## Update the Designer Configuration File through the UI
|
||||
|
||||
As of **Q4 2024** the [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%})'s **Options** page contains a new section: **Assembly References**:
|
||||
|
||||
|
||||
|
||||
It contains a grid listing the currently registered assemblies, similar to the grid used in Data Connections section:
|
||||
It contains a grid listing the currently registered assemblies, similar to the grid used in the Data Connections section:
|
||||
|
||||
|
||||
|
||||
Adding an assembly by clicking the **Add** button will essentially open a new OpenFile dialog set to show *.dll and *.exe files. If the selected assembly is targeting a .NET version which is different than the current runtime, the following confirmation message occurs:
|
||||
Adding an assembly by clicking the **Add** button will open a new OpenFile dialog set to show *.dll and *.exe files. If the selected assembly is targeting a .NET version that is different than the current runtime, the following confirmation message occurs:
|
||||
|
||||
|
||||
|
||||
Closing the dialog will trigger the routine for registering assemblies in application configuration file and loading them in app domain.
|
||||
Closing the dialog will trigger the routine for registering assemblies in the application configuration file and loading them in the app domain.
|
||||
|
||||
Deleting an Assembly Reference is performed by clicking the "X" button:
|
||||
|
||||
.
|
||||
|
||||
Closing the dialog will trigger the routine for un-registering assemblies in application configuration file.
|
||||
Closing the dialog will trigger the routine for unregistering assemblies in the application configuration file.
|
||||
|
||||
>note Deleting an Assembly Reference in the Standalone Report Designer for .NET Framework requires restarting the application.
|
||||
> Deleting an Assembly Reference in the Standalone Report Designer for .NET Framework requires restarting the application.
|
||||
|
||||
## Manually Update the Designer Configuration File
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче