Update host-reports-service-in-.net-5.md (#1085)
* Update host-reports-service-in-.net-5.md * Update host-reports-service-in-.net-6-with-minimal-api.md * Update host-reports-service-in-.net-core-2.1-and-2.2.md * Update how-to-host-reports-service-in-asp.net-core-3.1.md * Update how-to-implement-the-reportscontroller-in-an-application.md * Update how-to-self-host-telerik-reporting-rest-web-api.md * Update overview.md * Update how-to-use-redis-storage.md * Update installation-approaches.md * Update third-party-dependencies.md * Update localization.md * Update overview.md * Update crystal-reports-converter.md * Update bookmarks.md * Update picturebox.md * Update textbox.md * Update structure.md * Update formatting.md * Update overview.md * Update using-html-from-telerik-radeditor.md * Update barchart-map.md * Update choropleth-map.md * Update overview.md * Update location-providers.md * Update overview.md * Update tile-providers.md * Update how-to-add-report-viewer-to-a-wpf-.net-core-project.md * Update how-to-add--manually-report-viewer-to-a-wpf-.net-framework-project.md * Update how-to-set-reportsource-for-report-viewers.md * Update excel-rendering-design-considerations.md * Update html-rendering-design-considerations.md * Update excel-rendering-design-considerations.md * Update exporting-and-reusing-style-sheets.md * Update overview.md * Update q1-2014-sp1.md * Update q2-2015-sp1.md * Update q2-2015.md * Update r1-2018-sp2.md
This commit is contained in:
Todor Arabadzhiev
GitHub
Родитель
09dde6ae76
Коммит
49efea12f6
|
|
@ -324,11 +324,16 @@ The [WinUI Report Viewer control]({%slug telerikreporting/using-reports-in-appli
|
|||
__Example of specifying the ReportSource declaratively__
|
||||
|
||||
````XAML
|
||||
<telerikReporting:ReportViewer x:Name="reportViewer" Grid.Row="1" ReportEngineConnection="engine=RestService;uri=http://localhost:59655/api/reports">
|
||||
<telerikReporting:ReportViewer.ReportSource>
|
||||
<telerikReportingCore:UriReportSource Uri="Dashboard.trdp" />
|
||||
</telerikReporting:ReportViewer.ReportSource>
|
||||
</telerikReporting:ReportViewer>
|
||||
<telerikReportingCore:ReportViewer x:Name="reportViewer" Grid.Row="1" ReportEngineConnection="engine=RestService;uri=http://localhost:59655/api/reports">
|
||||
<telerikReportingCore:ReportViewer.ReportSource>
|
||||
<telerikReportingCore:UriReportSource Uri="MyReport.trdp">
|
||||
<telerikReportingCore:ReportSource.Parameters>
|
||||
<telerikReportingCore:Parameter Name="ParameterName_01" Value="ParameterValue_01"/>
|
||||
<telerikReportingCore:Parameter Name="ParameterName_02" Value="ParameterValue_02"/>
|
||||
</telerikReportingCore:ReportSource.Parameters>
|
||||
</telerikReportingCore:UriReportSource>
|
||||
</telerikReportingCore:ReportViewer.ReportSource>
|
||||
</telerikReportingCore:ReportViewer>
|
||||
````
|
||||
|
||||
## Set up Report Viewer controls that are integrated with Telerik Report Server
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ This article explains the steps needed to manually create an application which u
|
|||
+ *Telerik.Windows.Controls.Input.dll*
|
||||
+ *Telerik.Windows.Controls.Navigation.dll*
|
||||
+ *Telerik.Windows.Data.dll*
|
||||
|
||||
|
||||
In case you are still not prepared to migrate to *Implicit Styling*, you can use the binaries that include the XAML. However, you will still have to merge all the XAML files mentioned in the next step, otherwise, the Report Viewer will not show up as it will have no styling.
|
||||
|
||||
In case [Telerik UI for WPF](https://www.telerik.com/products/wpf/overview.aspx) is used only for the WPF Report Viewer, reference the *Telerik UI for WPF* assemblies available with Telerik Reporting. They are internally unlocked for the WPF Report Viewer but can only be used with the report viewer. The `.NET Framework` assemblies containing *Telerik UI for WPF* are located in `%programfiles(x86)%\Progress\Telerik Reporting {{site.suiteversion}}\Bin\WpfViewerDependencies\Framework`.
|
||||
|
|
@ -75,15 +75,11 @@ In case you use *Telerik UI for WPF* version greater than the __latest official
|
|||
## How to add the WPF ReportViewer to the toolbox
|
||||
|
||||
1. Select a WPF window file (e.g. `Window1.xaml`).
|
||||
|
||||
1. Open the toolbox and add your own tab or click on the General tab.
|
||||
|
||||
1. Right click in the selected tab area and select **Choose Items…** from the context menu.
|
||||
|
||||
1. The previous step will open **Choose Toolbox Items** dialog. Select the **WPF Components** tab and find the **ReportViewer** component from the **Telerik.ReportViewer.Wpf** assembly.
|
||||
|
||||
1. Click **OK**.
|
||||
|
||||
## See Also
|
||||
|
||||
* [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%})
|
||||
* [Adding Report Viewer to a WPF .NET Framework Project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%})
|
||||
|
|
|
|||
|
|
@ -73,19 +73,24 @@ xmlns:tr="http://schemas.telerik.com/wpf"
|
|||
|
||||
1. Add the WPF Report Viewer declaration to the target Window and set the proper UriReportSource.Uri relative path.
|
||||
|
||||
+ When using an __Embedded Reporting engine__ :
|
||||
+ When using an __Embedded Reporting engine__:
|
||||
|
||||
Reference a descriptive report definition (TRDP or TRDX report) from a local folder, or type report definition (CS or VB report) from a report library project. For example, add a new folder named *Reports* in the application main folder, copy your TRDP reports there, and reference one of them. Don't forget to set their property 'Copy to Output Directory' to 'Copy always' or 'Copy if newer':
|
||||
|
||||
````XAML
|
||||
<tr:ReportViewer Grid.Row="1" x:Name="ReportViewer1" HorizontalAlignment="Stretch">
|
||||
<tr:ReportViewer.ReportSource>
|
||||
<telerikReporting:UriReportSource Uri="Reports\MyReportName.trdp" />
|
||||
<telerikReporting:UriReportSource Uri="Reports\MyReportName.trdp">
|
||||
<telerikReporting:ReportSource.Parameters>
|
||||
<telerikReporting:Parameter Name="ParameterName_01" Value="ParameterValue_01"/>
|
||||
<telerikReporting:Parameter Name="ParameterName_02" Value="ParameterValue_02"/>
|
||||
</telerikReporting:ReportSource.Parameters>
|
||||
</telerikReporting:UriReportSource>
|
||||
</tr:ReportViewer.ReportSource>
|
||||
</tr:ReportViewer>
|
||||
````
|
||||
|
||||
+ When using a __Telerik Reporting REST Service__ :
|
||||
+ When using a __Telerik Reporting REST Service__:
|
||||
|
||||
The reports get rendered server-side and need to be accessible by the service. For that reason, you need to reference a descriptive report definition (TRDP or TRDX report) from a folder accessible by the service, or type report definition (CS or VB report) from a report library project that is accessible by the service.
|
||||
|
||||
|
|
@ -93,14 +98,19 @@ xmlns:tr="http://schemas.telerik.com/wpf"
|
|||
<tr:ReportViewer Grid.Row="1" x:Name="ReportViewer1" HorizontalAlignment="Stretch"
|
||||
ReportEngineConnection="engine=RestService;uri=http://localhost:59654/api/reports;timeout=100;keepClientAlive=True">
|
||||
<tr:ReportViewer.ReportSource>
|
||||
<telerikReporting:UriReportSource Uri="MyReportName.trdp" />
|
||||
<telerikReporting:UriReportSource Uri="MyReportName.trdp">
|
||||
<telerikReporting:ReportSource.Parameters>
|
||||
<telerikReporting:Parameter Name="ParameterName_01" Value="ParameterValue_01"/>
|
||||
<telerikReporting:Parameter Name="ParameterName_02" Value="ParameterValue_02"/>
|
||||
</telerikReporting:ReportSource.Parameters>
|
||||
</telerikReporting:UriReportSource>
|
||||
</tr:ReportViewer.ReportSource>
|
||||
</tr:ReportViewer>
|
||||
````
|
||||
|
||||
With the above setting, the REST Service running on `http://localhost:59654/api/reports` will look for the report named "MyReportName.trdp" in the folder specified as an argument of the [UriReportSourceResolver](/api/Telerik.Reporting.Services#Telerik_Reporting_Services_UriReportSourceResolver_System_String_) constructor.
|
||||
|
||||
+ When using a __Telerik Report Server__ :
|
||||
+ When using a __Telerik Report Server__:
|
||||
|
||||
The reports will be rendered by the Report Server. For that reason, you need to reference a descriptive report definition (TRDP or TRDX report) that is hosted on the server.
|
||||
|
||||
|
|
@ -109,6 +119,11 @@ xmlns:tr="http://schemas.telerik.com/wpf"
|
|||
ReportEngineConnection="engine=ReportServer;uri=http://yourreportserver:83/;username=yourusername;password=yourpassword">
|
||||
<tr:ReportViewer.ReportSource>
|
||||
<telerikReporting:UriReportSource Uri="MyCategory/MyReportName.trdp" />
|
||||
<telerikReporting:ReportSource.Parameters>
|
||||
<telerikReporting:Parameter Name="ParameterName_01" Value="ParameterValue_01"/>
|
||||
<telerikReporting:Parameter Name="ParameterName_02" Value="ParameterValue_02"/>
|
||||
</telerikReporting:ReportSource.Parameters>
|
||||
</telerikReporting:UriReportSource>
|
||||
</tr:ReportViewer.ReportSource>
|
||||
</tr:ReportViewer>
|
||||
````
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ ReportingEngineConfiguration = sp.GetService<IConfiguration>()
|
|||
|
||||
will be initialized from `appSettings.json` or `appsettings.{EnvironmentName}.json`.
|
||||
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
|
||||
In this guide we will create a helper class loading the json-formatted setting:
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ ReportingEngineConfiguration = sp.GetService<IConfiguration>();
|
|||
|
||||
will be initialized from `appSettings.json` or `appsettings.{EnvironmentName}.json`.
|
||||
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
|
||||
In this guide we will create a helper method loading the json-formatted setting:
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ ReportingEngineConfiguration = sp.GetService<IConfiguration>()
|
|||
|
||||
will be initialized from `appSettings.json` or `appsettings.{EnvironmentName}.json`.
|
||||
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
|
||||
In this guide we will create a helper class loading the json-formatted setting:
|
||||
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ ReportingEngineConfiguration = sp.GetService<IConfiguration>()
|
|||
|
||||
will be initialized from `appSettings.json` or `appsettings.{EnvironmentName}.json`.
|
||||
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
To activate JSON file configuration with a different name, for example, `reportingAppSettings.json`, call the [AddJsonFile](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.jsonconfigurationextensions.addjsonfile?view=dotnet-plat-ext-7.0) extension method on an instance of [ConfigurationBuilder](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.configuration.configurationbuilder?view=dotnet-plat-ext-7.0).
|
||||
|
||||
In this guide we will create a helper class loading the json-formatted setting:
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ The Telerik Reporting REST Web API service is represented by the abstract [Repor
|
|||
{{source=CodeSnippets\MvcCS\Controllers\ReportsController.cs region=ReportsControllerImplementation}}
|
||||
{{source=CodeSnippets\MvcVB\Controllers\ReportsController.vb region=ReportsControllerImplementation}}
|
||||
|
||||
[ReportsControllerBase](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase) inherits [System.Web.Http.ApiController](http://msdn.microsoft.com/en-us/library/system.web.http.apicontroller.aspx) and implements all necessary API actions. The provided sample implementation will resolve.trdx|.trdp report definitions from the Reports subfolder of the hosting ASP.NET application root. Other option is to reference a reports library and provide report [type assembly qualified name](http://msdn.microsoft.com/en-us/library/system.type.assemblyqualifiedname.aspx) from the service clients.
|
||||
[ReportsControllerBase](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase) inherits [System.Web.Http.ApiController](https://learn.microsoft.com/en-us/dotnet/api/system.web.http.apicontroller?view=aspnet-webapi-5.2) and implements all necessary API actions. The provided sample implementation will resolve.trdx|.trdp report definitions from the Reports subfolder of the hosting ASP.NET application root. Other option is to reference a reports library and provide report [type assembly qualified name](https://learn.microsoft.com/en-us/dotnet/api/system.type.assemblyqualifiedname?view=net-7.0) from the service clients.
|
||||
|
||||
>note Do not forget to add all necessary (i.e., referred from the report definitions) connection strings to the application configuration file.
|
||||
|
||||
|
|
@ -49,10 +49,8 @@ The Telerik Reporting REST Web API service is represented by the abstract [Repor
|
|||
{{source=CodeSnippets\MvcCS\Controllers\ReportsControllerConfigSection.cs region=ReportsControllerConfigSectionImplementation}}
|
||||
{{source=CodeSnippets\MvcVB\Controllers\ReportsControllerConfigSection.vb region=ReportsControllerConfigSectionImplementation}}
|
||||
|
||||
|
||||
Then add the __restReportService__ configuration element containing the service settings to the [Telerik Reporting Configuration Section]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/overview%}).
|
||||
|
||||
{{source=CodeSnippets\MvcCS\ReportServiceConfigurationSnippets\ConfigSectionConfiguration.xml}}
|
||||
|
||||
|
||||
For more information see [restReportService Element]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/restreportservice-element%}).
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ ASP.NET Web API does not require IIS. You can self-host a Web API in your own ho
|
|||
`netsh http add urlacl url=http://+:8080/ user=DOMAIN\user`
|
||||
|
||||
1. On Visual Studio, create a “Console Application” project
|
||||
1. Install the [Microsoft.AspNet.WebApi.SelfHost 4.0.30506](http://www.nuget.org/packages/Microsoft.AspNet.WebApi.SelfHost/4.0.30506) NuGet package
|
||||
1. Install the [Microsoft.AspNet.WebApi.SelfHost 4.0.30506](https://www.nuget.org/packages/Microsoft.AspNet.WebApi.SelfHost/4.0.30506) NuGet package
|
||||
|
||||
>The Reporting REST WebAPI Service is built against WebAPI 1. In case you have to use __newer version of Microsoft.AspNet.WebApi.SelfHost (e.g. WebAPI 2)__ you have to redirect the System.Web.Http and System.Net.Http.Formatting to their newer version. To do this, add the following bindingRedirects to your app.config and replace 5.1.0.0 with the exact version:
|
||||
>
|
||||
|
|
@ -54,7 +54,6 @@ ASP.NET Web API does not require IIS. You can self-host a Web API in your own ho
|
|||
+ System.Net.Http.Formatting.dll
|
||||
|
||||
1. Implement the reports controller as explained in the article [How to implement the ReportsController in an application]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-web-api-implementation/how-to-implement-the-reportscontroller-in-an-application%})
|
||||
|
||||
1. Implement the starting point of the application:
|
||||
|
||||
{{source=CodeSnippets\MvcCS\SelfHostedSnippets\Program.cs region=SelfHostedRestService}}
|
||||
|
|
@ -62,7 +61,6 @@ ASP.NET Web API does not require IIS. You can self-host a Web API in your own ho
|
|||
|
||||
|
||||
1. Run the console app
|
||||
|
||||
1. To verify whether the service works correctly you can make a sample request for the available document formats using the following URL:
|
||||
|
||||
`http://localhost: [portnumber]/api/reports/formats`
|
||||
|
|
|
|||
|
|
@ -32,8 +32,7 @@ The Reporting REST Service's resolver is used when resolving information for a r
|
|||
## Available built-in ReportSource Resolver implementations:
|
||||
|
||||
1. [UriReportSourceResolver](/api/Telerik.Reporting.Services.UriReportSourceResolver) - resolves absolute path UriReportSource from absolute or relative path to declarative report definition files. These are the `TRDX`, `TRDP` or `TRBP` files created in the [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) or [Web Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}).
|
||||
|
||||
1. [TypeReportSourceResolver](/api/Telerik.Reporting.Services.TypeReportSourceResolver) - resolves TypeReportSource from report type's [assembly qualified name](http://msdn.microsoft.com/en-us/library/30wyt9tk) (reports created in Visual Studio Report Designer).
|
||||
1. [TypeReportSourceResolver](/api/Telerik.Reporting.Services.TypeReportSourceResolver) - resolves TypeReportSource from report type's [assembly qualified name](https://learn.microsoft.com/en-us/dotnet/api/system.type.assemblyqualifiedname?view=net-7.0) (reports created in Visual Studio Report Designer).
|
||||
|
||||
> When working with other types of report sources for which there is no built-in report source resolver implementation, use a [Custom ReportSource Resolver]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-service-report-source-resolver/how-to-implement-a-custom-report-source-resolver%}) implementation. For example, when using [Drillthrough Report Action]({%slug telerikreporting/designing-reports/adding-interactivity-to-reports/actions/drillthrough-report-action%}) with [XmlReportSource](/api/Telerik.Reporting.XmlReportSource) the action will not work unless a custom report source resolver which can handle [XmlReportSource](/api/Telerik.Reporting.XmlReportSource) has been implemented.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Add NuGet package reference to `Telerik.Reporting.Cache.StackExchangeRedis` or `
|
|||
|
||||
+ In your application project add reference to the [StackExchange.Redis.StrongName](https://www.nuget.org/packages/StackExchange.Redis.StrongName) (not to be mistaken with StackExchange.Redis) NuGet package with version 1.0.320 or greater. This will add a dll reference to StackExchange.Redis.StrongName.dll version 1.0.316.0 or greater.
|
||||
|
||||
>When using greater version, a [binding redirect](https://msdn.microsoft.com/en-us/library/eftw1fys(v=vs.110).aspx) should be added in the application configuration file to the currently referenced dll version.
|
||||
>When using greater version, a [binding redirect](https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element) should be added in the application configuration file to the currently referenced dll version.
|
||||
|
||||
+ Add reference to the `Telerik.Reporting.Cache.StackExchangeRedis` library located in the {Telerik Reportng installation folder}/Bin folder.
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ Add NuGet package reference to `Telerik.Reporting.Cache.StackExchangeRedis` or `
|
|||
|
||||
+ In your application project add reference to the [StackExchange.Redis](https://www.nuget.org/packages/StackExchange.Redis) NuGet package with version 2.0.601 or greater. This will add a dll reference to StackExchange.Redis.dll.
|
||||
|
||||
>When using greater version, a [binding redirect](https://msdn.microsoft.com/en-us/library/eftw1fys(v=vs.110).aspx) should be added in the application configuration file to the currently referenced dll version.
|
||||
>When using greater version, a [binding redirect](https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element) should be added in the application configuration file to the currently referenced dll version.
|
||||
|
||||
+ Add reference to the `Telerik.Reporting.Cache.StackExchangeRedis.2` library located in the {Telerik Reportng installation folder}/Bin/netstandard2.0 folder.
|
||||
|
||||
|
|
@ -50,3 +50,4 @@ Where needed in your application create an instance of the [RedisStorage](/repor
|
|||
|
||||
* [Overview]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-service-storage/overview%})
|
||||
* [REST Report Service Configuration]({%slug telerikreporting/using-reports-in-applications/export-and-configure/configure-the-report-engine/restreportservice-element%})
|
||||
* [Binding Redirect](https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element)
|
||||
|
|
|
|||
|
|
@ -47,16 +47,16 @@ To install Telerik Reporting through the MSI automatic installer file:
|
|||
|
||||
1. In the dialog that opens, select the features you require.
|
||||
|
||||
+ If Telerik Reporting does not locate a local SQL server instance on your machine or if your SQL browser service is stopped, the examples from the __Examples__ dialog option will be installed but the configuration files for the application will not have valid connection strings. However, you can still access the working demos on the [Telerik Reporting Demos page](http://demos.telerik.com/reporting).
|
||||
+ If Telerik Reporting does not locate a local SQL server instance on your machine or if your SQL browser service is stopped, the examples from the __Examples__ dialog option will be installed but the configuration files for the application will not have valid connection strings. However, you can still access the working demos on the [Telerik Reporting Demos page](https://demos.telerik.com/reporting).
|
||||
+ To set up the examples and the used connection string, select __Examples Setup__. All local SQL Server 2005+ instances are supported.
|
||||
+ The examples use the MS SQL Server [AdventureWorks database](https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008/ms124659(v=sql.100)). Unless already available on your machine, the AdventureWorks database will also be deployed locally.
|
||||
+ The examples use the MS SQL Server [AdventureWorks database](https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2008/ms124659(v=sql.100)). Unless already available on your machine, the AdventureWorks database will also be deployed locally.
|
||||
+ Alternatively, you can install AdventureWorks by manually executing the SQL script from the installer. To use this option, navigate to __[InstallDir]/Examples/Data/AdventureWorks OLTP__. For the script to run correctly, uncomment the `SET @data_path = 'C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks OLTP\';` statement and specify the correct path to the CSV data files which are in the same folder as the SQL script file.
|
||||
|
||||
|
||||
|
||||
1. (If __Examples Setup__ was selected) In the __Setup Wizard__ dialog, select your __Database Server__ and the authentication for the connection. The Wizard detects all running instances and lists them in the input field.
|
||||
1. (If __Examples Setup__ was selected) In the __Setup Wizard__ dialog, select your __Database Server__ and the authentication for the connection. The Wizard detects all running instances and lists them in the input field.
|
||||
|
||||
> To enable the Wizard to detect all running SQL Server instances, run the [SQL Server Browser Service](https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms181087(v=sql.105)).
|
||||
> To enable the Wizard to detect all running SQL Server instances, run the [SQL Server Browser Service](https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms181087(v=sql.105)).
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -28,10 +28,9 @@ To export its reports in Open XML formats, such as `.docx`, `.xlsx`, or `.pptx`,
|
|||
The `DocumentFormat.OpenXml` assembly has two versions with different Public Key Tokens. To provide support for both, Telerik Reporting delivers the following `Telerik.Reporting.OpenXmlRendering` assemblies:
|
||||
|
||||
* `Telerik.Reporting.OpenXmlRendering.dll`−Supports 2.0.5022.0 and 2.5.5631.0 `DocumentFormat.OpenXml.dll` versions.
|
||||
|
||||
* `Telerik.Reporting.OpenXmlRendering.2.7.2.dll`−Supports 2.7.2.0 and later `DocumentFormat.OpenXml.dll` versions.
|
||||
|
||||
> To generate compatible document types, always use the latest available version. To use later versions other than the versions previously listed, add [`bindingRedirect`](http://msdn.microsoft.com/en-us/library/eftw1fys(v=vs.110).aspx) for `DocumentFormat.OpenXml.dll` assembly to the configuration file of the application.
|
||||
> To generate compatible document types, always use the latest available version. To use later versions other than the versions previously listed, add [`bindingRedirect`](https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element) for `DocumentFormat.OpenXml.dll` assembly to the configuration file of the application.
|
||||
|
||||
To download Open XML by using the NuGet feed, refer to the [`DocumentFormat.OpenXml` NuGet package](https://www.nuget.org/packages/DocumentFormat.OpenXml/).
|
||||
|
||||
|
|
|
|||
|
|
@ -13,56 +13,46 @@ position: 12
|
|||
|
||||
Localization is used to display the reports in the language of a specific culture. The article elaborates how to localize reports with resource files. The resource files format depends on the used Report Designer:
|
||||
|
||||
* [Visual Studio Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/overview%}) - RESX files. They are siblings to the report code file in the file system. For more information on the RESX file format see [Resources in.Resx File Format ](https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-3.0/ekyft91f(v=vs.85))
|
||||
* [Visual Studio Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/overview%}) - RESX files. They are siblings to the report code file in the file system. For more information on the RESX file format see [Resources in.Resx File Format ](https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-3.0/ekyft91f(v=vs.85))
|
||||
* [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) - RES files that are part of the TRDP archive. The RES files contain a key-value list. The first row begins with a __key__ after the key follows whitespace and the __value__ surrounded in double quotation mark. After the last unescaped double quotation mark follows a new line. The key cannot contain any whitespace characters. The value can contain any character including whitespaces and double quotation mark but the double quotation mark should be escaped with another double quotation mark.
|
||||
|
||||
* [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) - RES files that are part of the TRDP archive. The RES files contain a key-value list. The first row begins with a __key__ after the key follows whitespace and the __value__ surrounded in double quotation mark. After the last unescaped double quotation mark follows a new line. The key cannot contain any whitespace characters. The value can contain any character including whitespaces and double quotation mark but the double quotation mark should be escaped with another double quotation mark.
|
||||
|
||||
>note The Standalone Report Designer supports two XML report formats (TRDP and TRDX). The localization mechanism described in this article is supported only in the TRDP report format. Currently, no out of the box solution is available for localizing TRDX report definitions. If TRDX report format with localization is required the recommended approach is to create a [user function](/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions) that will accept resource key and optionally [string report parameter](/designing-reports/connecting-to-data/report-parameters/overview) specifying the culture code and return a localized string that is used for the report item property value.
|
||||
>note The Standalone Report Designer supports two XML report formats (TRDP and TRDX). The localization mechanism described in this article is supported only in the TRDP report format. Currently, no out of the box solution is available for localizing TRDX report definitions. If TRDX report format with localization is required the recommended approach is to create a [user function](/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions) that will accept resource key and optionally [string report parameter](/designing-reports/connecting-to-data/report-parameters/overview) specifying the culture code and return a localized string that is used for the report item property value.
|
||||
|
||||
* [Web Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/web-report-designer/overview%}) - The Web Report Designer doesn't support localization.
|
||||
|
||||
>important __known issue__: The Web Report Designer doesn't expose the _Localizable_ and _Language_ properties of the Report. If you modify the Report in the web designer and save it, it will serialize it without these properties. For that reason, the Report localization informaton will be entirely removed.
|
||||
>important __known issue__: The Web Report Designer doesn't expose the _Localizable_ and _Language_ properties of the Report. If you modify the Report in the web designer and save it, it will serialize it without these properties. For that reason, the Report localization informaton will be entirely removed.
|
||||
|
||||
Telerik Reporting uses a similar methodology for localization as Visual Studio uses for Windows Forms. The designer lets you define static text for the report (e.g. column headings, titles) in each language that you specify. A resource file is automatically created for each language to store translated text. For more background information on localizing applications see the MSDN article [Globalizing and Localizing Applications](https://msdn.microsoft.com/en-us/library/1021kkz0.aspx).
|
||||
Telerik Reporting uses a similar methodology for localization as Visual Studio uses for Windows Forms. The designer lets you define static text for the report (e.g. column headings, titles) in each language that you specify. A resource file is automatically created for each language to store translated text. For more background information on localizing applications see the MSDN article [Globalizing and Localizing Applications](https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2015/ide/globalizing-and-localizing-applications?view=vs-2015).
|
||||
|
||||
>caption Localized documents displayed in English and Spanish (see figure below):
|
||||
|
||||
|
||||
|
||||
|
||||
To localize a report:
|
||||
|
||||
1. In the designer set the Report __Localizable__ property to true. If at any point the __Localizable__ property is set to false all the resource files are deleted and the report property values are filled with the currently selected language values.
|
||||
1. In the designer set the Report __Localizable__ property to true. If at any point the __Localizable__ property is set to false all the resource files are deleted and the report property values are filled with the currently selected language values.
|
||||
1. Select a __Language__ property value from the drop-down list in the properties window.
|
||||
1. Set the target component Name property. Keeping the default auto generated name can result in new items inheriting deleted items localized values.
|
||||
1. Translate the static text into the desired language indicated by the __Language__ property.
|
||||
|
||||
1. Select a __Language__ property value from the drop-down list in the properties window.
|
||||
>important Items cannot be added in localization mode. After localizing the report set the Language property to (Default) to add new items.
|
||||
|
||||
1. Set the target component Name property. Keeping the default auto generated name can result in new items inheriting deleted items localized values.
|
||||
The report's runtime localization depends on the current thread's culture UI setting and must be already set in order the report to be processed with the correct resources.
|
||||
|
||||
1. Translate the static text into the desired language indicated by the __Language__ property.
|
||||
The current thread's culture UI setting depends on the OS or the browser language settings.
|
||||
|
||||
>important Items cannot be added in localization mode. After localizing the report set the Language property to (Default) to add new items.
|
||||
|
||||
|
||||
The report's runtime localization depends on the current thread's culture UI setting and must be already set in order the report to be processed with the correct resources.
|
||||
|
||||
The current thread's culture UI setting depends on the OS or the browser language settings.
|
||||
|
||||
To run the localized report in a specific language that is different from the thread's current culture UI setting:
|
||||
To run the localized report in a specific language that is different from the thread's current culture UI setting:
|
||||
|
||||
1. Add Threading and Globalization namespaces to your application.
|
||||
1. Set the current thread __CurrentUICulture__ to a new instance of __CultureInfo__. The __CultureInfo__ constructor takes the culture code of the language you want to display. For example "en-US" for United States English or "es-MX" for Mexican Spanish.
|
||||
1. Optionally you can set the __CurrentCulture__ for the current thread to the culture code of the language you wish to display. __CurrentCulture__ affects dynamic data such as date, time and money formats. The "Birth Date" column date format in the figure above shows Month/Day/Year in English, but in Day/Month/Year format in the Spanish example.
|
||||
1. Create a [report source object]({%slug telerikreporting/designing-reports/report-sources/overview%}) to specify the report, and assign it to the __ReportViewer.ReportSource__ property. If you are using a __ReportViewer__ in a Windows application, call the __ReportViewer.RefreshReport()__ method. If you are using a web viewer, let the page send the request for getting the rendered report.
|
||||
|
||||
1. Set the current thread __CurrentUICulture__ to a new instance of __CultureInfo__. The __CultureInfo__ constructor takes the culture code of the language you want to display. For example "en-US" for United States English or "es-MX" for Mexican Spanish.
|
||||
|
||||
1. Optionally you can set the __CurrentCulture__ for the current thread to the culture code of the language you wish to display. __CurrentCulture__ affects dynamic data such as date, time and money formats. The "Birth Date" column date format in the figure above shows Month/Day/Year in English, but in Day/Month/Year format in the Spanish example.
|
||||
|
||||
1. Create a [report source object]({%slug telerikreporting/designing-reports/report-sources/overview%}) to specify the report, and assign it to the __ReportViewer.ReportSource__ property. If you are using a __ReportViewer__ in a Windows application, call the __ReportViewer.RefreshReport()__ method. If you are using a web viewer, let the page send the request for getting the rendered report.
|
||||
|
||||
>important Note that the culture settings must be applied before creating an instance of the report. This ensures the correct report's resource file will be used on processing the document.
|
||||
|
||||
>important Note that the culture settings must be applied before creating an instance of the report. This ensures the correct report's resource file will be used on processing the document.
|
||||
|
||||
{{source=CodeSnippets\CS\API\Telerik\Reporting\LocalizationSnippets.cs region=SetThreadCulture}}
|
||||
{{source=CodeSnippets\VB\API\Telerik\Reporting\LocalizationSnippets.vb region=SetThreadCulture}}
|
||||
|
||||
|
||||
## Centralizing the localization of reports
|
||||
|
||||
Big applications with many reports tend to be hard to localize with the provided approach above, in such cases the recommended approach is creating a [User Function]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions%}) that accepts a resource key and optionally a string report parameter specifying the culture code. The function will return a localized string that is used for the report item property value.
|
||||
Big applications with many reports tend to be hard to localize with the provided approach above, in such cases the recommended approach is creating a [User Function]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/extending-expressions/user-functions%}) that accepts a resource key and optionally a string report parameter specifying the culture code. The function will return a localized string that is used for the report item property value.
|
||||
|
|
|
|||
|
|
@ -11,13 +11,13 @@ position: 11
|
|||
|
||||
# Report Globalization Overview
|
||||
|
||||
Telerik Reporting offers the possibility to control the way numbers, dates and currencies are displayed and to layout text in different directions.
|
||||
Telerik Reporting offers the possibility to control the way numbers, dates and currencies are displayed and to layout text in different directions.
|
||||
|
||||
A report is globalized with the help of a [System.Globalization.CultureInfo](http://msdn2.microsoft.com/en-us/library/system.globalization.cultureinfo.aspx) object. You can specify a Culture for the entire [Telerik.Reporting.Report](/api/Telerik.Reporting.Report) by setting its [Telerik.Reporting.Report.Culture](/api/Telerik.Reporting.Report#Telerik_Reporting_Report_Culture) property. This will force all [Telerik.Reporting.TextBox](/api/Telerik.Reporting.TextBox) items to respect the assigned Culture. But you are not limited by one culture per report. You can mix an unlimited number of cultures, by setting the [Telerik.Reporting.TextItemBase.Culture](/api/Telerik.Reporting.TextItemBase#Telerik_Reporting_TextItemBase_Culture) property of a specific [Telerik.Reporting.TextBox](/api/Telerik.Reporting.TextBox). This will override the Report's Culture.
|
||||
A report is globalized with the help of a [System.Globalization.CultureInfo](https://learn.microsoft.com/en-us/dotnet/api/system.globalization.cultureinfo?view=net-7.0) object. You can specify a Culture for the entire [Telerik.Reporting.Report](/api/Telerik.Reporting.Report) by setting its [Telerik.Reporting.Report.Culture](/api/Telerik.Reporting.Report#Telerik_Reporting_Report_Culture) property. This will force all [Telerik.Reporting.TextBox](/api/Telerik.Reporting.TextBox) items to respect the assigned Culture. But you are not limited by one culture per report. You can mix an unlimited number of cultures, by setting the [Telerik.Reporting.TextItemBase.Culture](/api/Telerik.Reporting.TextItemBase#Telerik_Reporting_TextItemBase_Culture) property of a specific [Telerik.Reporting.TextBox](/api/Telerik.Reporting.TextBox). This will override the Report's Culture.
|
||||
|
||||
## Culture Inheritance
|
||||
|
||||
When determining what Culture to use for formatting strings and text direction, the rendering engine will inspect the those objects in the following order:
|
||||
When determining what Culture to use for formatting strings and text direction, the rendering engine will inspect the those objects in the following order:
|
||||
|
||||
1. The Culture of the __TextBox__.
|
||||
1. If the TextBox has no Culture defined, the Culture of the __Report__ is used.
|
||||
|
|
@ -33,7 +33,7 @@ Culture affects the way strings are formatted in Telerik Reporting. For example,
|
|||
|
||||
* __Text Direction (LTR/RTL)__
|
||||
|
||||
Middle Eastern languages such as Hebrew and Arabic are generally written from right to left. If your TextBox will contain text written using a RTL script, then you simply need to specify the appropriate Culture, for example "he" for Hebrew and "ar" for Arabic.
|
||||
Middle Eastern languages such as Hebrew and Arabic are generally written from right to left. If your TextBox will contain text written using a RTL script, then you simply need to specify the appropriate Culture, for example "he" for Hebrew and "ar" for Arabic.
|
||||
|
||||
## See Also
|
||||
|
||||
|
|
|
|||
|
|
@ -11,41 +11,29 @@ previous_url: /crystal-reports-converter
|
|||
|
||||
# Converting SAP Crystal Reports
|
||||
|
||||
|
||||
This article explains how to convert a report created with SAP Crystal Reports to Telerik Reporting report definition.
|
||||
|
||||
## Changes Information
|
||||
|
||||
The Telerik Crystal Reports Converter is built against Crystal Reports 13.0.20.2399. In case you need to convert a Crystal Reports definition that has version lower than 13.0.2000, please use Telerik Reporting R3 2019 or earlier and check this KB article for more details: [Converting reports from various versions of CrystalReports]({%slug converting-reports-from-various-versions-of-crystalreports%}).
|
||||
|
||||
|
||||
|
||||
|
||||
## Conversion Process
|
||||
|
||||
The converter iterates through all the items in a Crystal Report (CR) instance and tries to map each report object to its corresponding item in Telerik Reporting. Unfortunately, the.NET model classes that represent the native Crystal Reports objects often do not expose all the properties of its underlying objects, which makes the complete conversion unattainable. The size, location and styling of each CR object are converted as close as possible to the original. The specific object properties are listed below:
|
||||
|
||||
* __Report structure__ - the header, footer and details report sections are converted to their exact equivalents in Telerik Reporting. The visibility and suppression of the sections is not converted. The group headers and footers are converted into group sections in Telerik Reporting.
|
||||
|
||||
* __Data connections__ – the supported connection types are OLEDB and ODBC. The converter creates a new SQLDataSource instance for each command created in Database Expert and sets its attributes like connection string, command text and parameters. If the data connection used in the source report does not have dedicated command or stored procedure, the converter will generate a *select * from {tableName}* statement for the SqlDataSource instance's CommandText property.
|
||||
|
||||
* __Report parameters__ – if the data command used in Crystal report has parameters, they will be converted as report parameters, regarding their type, visibility and default values.
|
||||
|
||||
* __Field objects__ – data-bound fields are converted to Telerik Reporting TextBox instances with their respective database field expressions, preserving the formatting.
|
||||
|
||||
* __Text objects__ – converted into Telerik Reporting TextBox instances with static text, preserving the formatting.
|
||||
|
||||
* __Summary fields__ – converted into Telerik Reporting TextBox instances. The converter recognizes and converts the following Crystal Reports summary expressions: *Sum, Count, Distinct Count, Minimum, Maximum, Average*.
|
||||
|
||||
* __Cross-Tab objects__ – the provided.NET model does not contain any properties that would allow to examine the Cross-Tab definition. The converted Telerik Reporting CrossTab item will have the same size and location, but default structure containing empty cells.
|
||||
|
||||
* __SubReport objects__ – the converter will create a Telerik Reporting SubReport item, preserving the size and location. The ReportSource property must be manually set.
|
||||
|
||||
* __Line and Box objects__ – converted to Telerik Reporting Shape items.
|
||||
|
||||
* __PictureBox objects__ – converted to Telerik Reporting PictureBox items. The converter will convert only PictureBox objects that obtain their image data from a database field.
|
||||
|
||||
* __Chart objects__ – converted to Telerik Reporting Graph items. Supported chart types are: column, pie, doughnut, line, area, scatter. The provided.NET model does not contain all the properties necessary to completely convert the chart item and default values are used instead. Such properties include stacked/clustered for column series and horizontal/vertical orientation of column charts.
|
||||
|
||||
* __Barcode__ – the default barcode implementation in Crystal Reports is achieved through text objects with specific barcode font that allows to create Code39-encoded barcodes. The converter generates Telerik Reporting Barcode items only for Crystal Reports text objects with font name that contains Code39 string.
|
||||
|
||||
* __Special fields__ - The converter recognizes and converts the following Crystal Reports special fields: *PrintDate, PrintTime, ModificationDate, ModificationTime, DataDate, DataTime, RecordNumber, PageNumber, TotalPageCount, Page N of M*.
|
||||
|
|
@ -54,49 +42,47 @@ The converter iterates through all the items in a Crystal Report (CR) instance a
|
|||
|
||||
In order to load the Crystal Reports assemblies needed for the conversion, proper binding redirects need to be added to the configuration file of the report designer application. When using the Standalone Report Designer, this file is *Telerik.ReportDesigner.exe.config* , placed in the *\Report Designer* subfolder of the product installation category. When using the Visual Studio Report Designer, this file is *devenv.exe.config* , placed in the *\Common7\Ide* subfolder of Visual Studio installation directory. The binding redirects need to point to the version of Crystal Reports runtime installed on the machine.
|
||||
|
||||
The Crystal Reports assemblies are stored in machine’s GAC (Global Assembly Cache). The GAC folder for.NET Framework v.4.0 and later is *%windir%\Microsoft.NET\assembly* , and for earlier versions is *%windir%\assembly*. Search the GAC for assemblies named *CrystalDecisions.Shared.dll* or *CrystalDecisions.CrystalReports.Engine.dll*. The assembly version can be obtained either from the assembly subfolder name, or by using the [gacutil.exe](https://docs.microsoft.com/en-us/dotnet/framework/tools/gacutil-exe-gac-tool):
|
||||
|
||||
```
|
||||
C:\WINDOWS\system32>gacutil -l CrystalDecisions.Shared
|
||||
Microsoft (R).NET Global Assembly Cache Utility. Version 4.0.30319.0
|
||||
Copyright (c) Microsoft Corporation. All rights reserved.
|
||||
The Global Assembly Cache contains the following assemblies:
|
||||
CrystalDecisions.Shared, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=MSIL
|
||||
```
|
||||
The Crystal Reports assemblies are stored in machine’s GAC (Global Assembly Cache). The GAC folder for.NET Framework v.4.0 and later is *%windir%\Microsoft.NET\assembly* , and for earlier versions is *%windir%\assembly*. Search the GAC for assemblies named *CrystalDecisions.Shared.dll* or *CrystalDecisions.CrystalReports.Engine.dll*. The assembly version can be obtained either from the assembly subfolder name, or by using the [gacutil.exe](https://learn.microsoft.com/en-us/dotnet/framework/tools/gacutil-exe-gac-tool):
|
||||
|
||||
````
|
||||
C:\WINDOWS\system32>gacutil -l CrystalDecisions.Shared
|
||||
Microsoft (R).NET Global Assembly Cache Utility. Version 4.0.30319.0
|
||||
Copyright (c) Microsoft Corporation. All rights reserved.
|
||||
The Global Assembly Cache contains the following assemblies:
|
||||
CrystalDecisions.Shared, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, processorArchitecture=MSIL
|
||||
````
|
||||
|
||||
The output from the *gacutil.exe* above shows that the current version of the installed Crystal Reports runtime assemblies is __13.0.3500.0__. Here is how the configuration file with added binding redirects will look like:
|
||||
|
||||
|
||||
````xml
|
||||
````XML
|
||||
<runtime>
|
||||
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
|
||||
...
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.Shared" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.Enterprise.Framework" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.Enterprise.InfoStore" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.ReportAppServer.DataDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.ReportAppServer.ReportDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
...
|
||||
</assemblyBinding>
|
||||
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.Shared" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.Enterprise.Framework" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.Enterprise.InfoStore" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.ReportAppServer.DataDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
<dependentAssembly>
|
||||
<assemblyIdentity name="CrystalDecisions.ReportAppServer.ReportDefModel" publicKeyToken="692fbea5521e1304" culture="neutral"/>
|
||||
<bindingRedirect oldVersion="0.0.0.0-13.0.3500.0" newVersion="13.0.3500.0"/>
|
||||
</dependentAssembly>
|
||||
...
|
||||
</assemblyBinding>
|
||||
</runtime>
|
||||
````
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ For example, if your report displays a table grouped by color, you would add a b
|
|||
|
||||
To define a bookmark on item/group use the [BookmarkId](/api/Telerik.Reporting.ReportItemBase#Telerik_Reporting_ReportItemBase_BookmarkId) property. To define a bookmark action add a [NavigateToBookmarkAction](/api/Telerik.Reporting.NavigateToBookmarkAction) on another item.
|
||||
|
||||
>important It is recommended that the `BookmarkId` property value is unique and conforms to the [C# Language Specification for Identifiers](https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/identifier-names). If the `BookmarkId` contains characters which are not allowed by this specification, they will be escaped by the reporting engine.
|
||||
>important It is recommended that the `BookmarkId` property value is unique and conforms to the [C# Language Specification for Identifiers](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/identifier-names). If the `BookmarkId` contains characters which are not allowed by this specification, they will be escaped by the reporting engine.
|
||||
|
||||
## How to Add Bookmarks to a Report item
|
||||
|
||||
|
|
@ -25,7 +25,6 @@ Add bookmarks to a report when you want to provide a customized table of content
|
|||
### Adding a bookmark to a report item
|
||||
|
||||
1. In __Design view__, select a report item to which you want to add a bookmark. The properties for the selected item appear in the __Properties__ pane.
|
||||
|
||||
1. In the [BookmarkId](/api/Telerik.Reporting.ReportItemBase#Telerik_Reporting_ReportItemBase_BookmarkId) property, type a string that is the label for this bookmark. Alternatively, click the ellipsis to open the Expression dialog box to specify an expression that evaluates to a label.
|
||||
|
||||
>note The [BookmarkId](/api/Telerik.Reporting.ReportItemBase#Telerik_Reporting_ReportItemBase_BookmarkId) can be any string, but it must be unique in the report. If the `BookmarkID` is not unique, an action to the bookmark finds the _first_ matching bookmark.
|
||||
|
|
@ -37,28 +36,21 @@ Add bookmarks to a report when you want to provide a customized table of content
|
|||
### Adding a bookmark to a Report group
|
||||
|
||||
1. In __Design view__, right click outside the report sections, select View and open up the [Group Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/group-explorer%}). Select a report group to which you want to add a bookmark. The properties for the selected group appear in the __Properties__ pane.
|
||||
|
||||
1. In the [BookmarkId](/api/Telerik.Reporting.Group#Telerik_Reporting_Group_BookmarkId) property,
|
||||
type a string that is the label for this bookmark. Alternatively, click
|
||||
the ellipsis to open the __Expression__ dialog box to specify an expression that evaluates to text.
|
||||
Typically for a group, the expression you type should be the group expression.
|
||||
1. In the [BookmarkId](/api/Telerik.Reporting.Group#Telerik_Reporting_Group_BookmarkId) property, type a string that is the label for this bookmark. Alternatively, click the ellipsis to open the __Expression__ dialog box to specify an expression that evaluates to text. Typically for a group, the expression you type should be the group expression.
|
||||
|
||||
>note The [BookmarkId](/api/Telerik.Reporting.Group#Telerik_Reporting_Group_BookmarkId) can be any string, but it must be unique in the report. If the `BookmarkID` is not unique, an action to the bookmark finds the first matching bookmark.
|
||||
|
||||
## How to Add Bookmarks to a Table group
|
||||
|
||||
Add bookmarks to a report when you want to provide a customized table of contents or to provide customized internal navigation in the report. Typically, you add bookmarks to locations in the report to which you want to direct users. You can create your own strings to use as bookmarks, or, for groups, you can set the bookmark to the group expression. After you create bookmarks, you can add report items that the user can click to go to each bookmark. These items are typically text boxes or images.
|
||||
Add bookmarks to a report when you want to provide a customized table of contents or to provide customized internal navigation in the report. Typically, you add bookmarks to locations in the report to which you want to direct users. You can create your own strings to use as bookmarks, or, for groups, you can set the bookmark to the group expression. After you create bookmarks, you can add report items that the user can click to go to each bookmark. These items are typically text boxes or images.
|
||||
|
||||
### Adding a bookmark to a Table group
|
||||
|
||||
1. In __Design view__, right click outside the report sections, select View and open up the [Group Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/group-explorer%}). Select a [Table](/api/Telerik.Reporting.Table), [Crosstab](/api/Telerik.Reporting.Crosstab) or [List](/api/Telerik.Reporting.List) report item, so the __Group Explorer__ shows the respective groups. Select a group to which you want to add a bookmark, right click on it and select __Group Properties__. The properties for the selected group appear in the __Edit Table Group__ dialog.
|
||||
|
||||
1. In the [BookmarkId](/api/Telerik.Reporting.TableGroup#Telerik_Reporting_TableGroup_BookmarkId) property,
|
||||
type a string that is the label for this bookmark. Alternatively, click the ellipsis to open the __Expression__ dialog box to
|
||||
specify an expression that evaluates to text. Typically for a group, the expression you type should be the group expression.
|
||||
1. In the [BookmarkId](/api/Telerik.Reporting.TableGroup#Telerik_Reporting_TableGroup_BookmarkId) property, type a string that is the label for this bookmark. Alternatively, click the ellipsis to open the __Expression__ dialog box to specify an expression that evaluates to text. Typically for a group, the expression you type should be the group expression.
|
||||
|
||||
>note The [BookmarkId](/api/Telerik.Reporting.TableGroup#Telerik_Reporting_TableGroup_BookmarkId) can be any string, but it must be unique in the report. If the `BookmarkID` is not unique, an action to the bookmark finds the first matching bookmark.
|
||||
|
||||
## See Also
|
||||
|
||||
* [Bookmark Action]({%slug telerikreporting/designing-reports/adding-interactivity-to-reports/actions/bookmark-action%})
|
||||
* [Bookmark Action]({%slug telerikreporting/designing-reports/adding-interactivity-to-reports/actions/bookmark-action%})
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ Depending on the series type, the Graph can visualize one or more measures:
|
|||
|
||||
## Coordinate Systems
|
||||
|
||||
The Graph item uses a two-dimensional [coordinate system](http://en.wikipedia.org/wiki/Coordinate_system) that uniquely identifies the position of each data point. Each coordinate system consists of two reference lines called "coordinate axes" (or just "axes") and an "origin".
|
||||
The Graph item uses a two-dimensional [coordinate system](https://en.wikipedia.org/wiki/Coordinate_system) that uniquely identifies the position of each data point. Each coordinate system consists of two reference lines called "coordinate axes" (or just "axes") and an "origin".
|
||||
|
||||
The Graph provides support for the Cartesian and Polar two-dimensional coordinate systems. Since there is a direct conversion between the two coordinate systems, they are interchangeable in the Graph report item. The coordinates of the data points in the Graph are represented by the `(x, y)` pair that for the Polar coordinate system is converted to `(ϴ, r)`, that is, `(x, y)` ⇔ `(ϴ, r)`.
|
||||
|
||||
|
|
@ -69,7 +69,7 @@ The coordinate system also defines the default appearance and style of the two a
|
|||
|
||||
### Cartesian
|
||||
|
||||
In a [Cartesian coordinate system](http://en.wikipedia.org/wiki/Cartesian_coordinate_system), each point is defined by an ordered pair of two coordinates which are the distances of the point to the two perpendicular axes.
|
||||
In a [Cartesian coordinate system](https://en.wikipedia.org/wiki/Cartesian_coordinate_system), each point is defined by an ordered pair of two coordinates which are the distances of the point to the two perpendicular axes.
|
||||
|
||||
The Cartesian coordinate system provides the following axes:
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ The Cartesian coordinate system provides the following axes:
|
|||
|
||||
### Polar
|
||||
|
||||
A [Polar coordinate system](http://en.wikipedia.org/wiki/Polar_coordinate_system) is used where each point on a plane is determined by a distance from the origin (called the radial coordinate or radius) and an angle from a fixed direction (the angular coordinate, polar angle, or azimuth).
|
||||
A [Polar coordinate system](https://en.wikipedia.org/wiki/Polar_coordinate_system) is used where each point on a plane is determined by a distance from the origin (called the radial coordinate or radius) and an angle from a fixed direction (the angular coordinate, polar angle, or azimuth).
|
||||
|
||||
The Polar coordinate system provides the following axes:
|
||||
|
||||
|
|
@ -116,7 +116,7 @@ A series represents a series of data points that represents individual measureme
|
|||
|
||||
### Bar Charts
|
||||
|
||||
[Bar charts](http://en.wikipedia.org/wiki/Bar_chart) display data points as bars to show comparisons between categories. One axis of the chart shows the specific categories being compared, and the other axis represents a discrete value.
|
||||
[Bar charts](https://en.wikipedia.org/wiki/Bar_chart) display data points as bars to show comparisons between categories. One axis of the chart shows the specific categories being compared, and the other axis represents a discrete value.
|
||||
|
||||
You can arrange the Bar series in different ways to emphasize various aspects of the data:
|
||||
|
||||
|
|
@ -129,13 +129,13 @@ In a Polar coordinate system the bars appears in a wedge shape. If the series ar
|
|||
|
||||
### Line Charts
|
||||
|
||||
[Line charts](http://en.wikipedia.org/wiki/Line_chart) display a series of data points connected by straight or smooth line segments. Data points are represented by markers that can vary by shape (circle, square, diamond, cross, and so on) and can display a third variable or measure with its size (also known as Bubble charts).
|
||||
[Line charts](https://en.wikipedia.org/wiki/Line_chart) display a series of data points connected by straight or smooth line segments. Data points are represented by markers that can vary by shape (circle, square, diamond, cross, and so on) and can display a third variable or measure with its size (also known as Bubble charts).
|
||||
|
||||
When a Line series is projected on a Polar coordinate system, the result is also known as a Radar or Spider Line chart. Line series may be stacked to show a cumulative effect (stacked or stacked 100%).
|
||||
|
||||
### Area Charts
|
||||
|
||||
[Area charts](http://en.wikipedia.org/wiki/Area_chart) are similar to the Line series. Area series display series of data points connected by straight or smooth line segments too but the area below the line is colored to indicate the volume.
|
||||
[Area charts](https://en.wikipedia.org/wiki/Area_chart) are similar to the Line series. Area series display series of data points connected by straight or smooth line segments too but the area below the line is colored to indicate the volume.
|
||||
|
||||
When an Area series is projected on a Polar coordinate system, the result is also known as a Radar or Spider Area chart. Area series may be stacked to show a cumulative effect (stacked or stacked 100%).
|
||||
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ The HtmlTextBox enables you to control the style of its text presentation by sup
|
|||
|
||||
## Supported HTML Tags
|
||||
|
||||
The following `HtmlTextBoxVarious` formatting options are available and provide control over the HtmlTextBox text presentation:
|
||||
The following `HtmlTextBoxVarious` formatting options are available and provide control over the HtmlTextBox text presentation:
|
||||
|
||||
* Font, color (`<font>`), and size (relative size against the font size of the item). The default size value is `3` out of the 1-7 range.
|
||||
* Font, color (`<font>`), and size (relative size against the font size of the item). The default size value is `3` out of the 1-7 range.
|
||||
* Bold, Italic, Underline (`<strong>`,`<b>`, `<em>`, `<i>`, and `<u>`).
|
||||
* Subscript, Superscript (`<sub>` and `<sup>`).
|
||||
* HyperLink (`<a href target>`).
|
||||
|
|
@ -27,11 +27,11 @@ While the HtmlTextBox does not support the `table` and `img` tags, you can use t
|
|||
|
||||
## Supported CSS Attributes
|
||||
|
||||
When you import text that contains HTML markup, the data is always parsed by the HtmlTextBox first. Because only a subset of HTML tags is supported, the HTML that is shown in the rendered report may differ from your original HTML.
|
||||
When you import text that contains HTML markup, the data is always parsed by the HtmlTextBox first. Because only a subset of HTML tags is supported, the HTML that is shown in the rendered report may differ from your original HTML.
|
||||
|
||||
Also, according to the HTML specification and the general XML specification, the `&`, `<` and `>` characters are considered as markup delimiters and you have to encode them so that they are treated as regular text. For example, you can escape the `&` character `& amp;` entity. For more information, refer to the [w3.org article](http://www.w3.org/TR/REC-xml/#syntax).
|
||||
Also, according to the HTML specification and the general XML specification, the `&`, `<` and `>` characters are considered as markup delimiters and you have to encode them so that they are treated as regular text. For example, you can escape the `&` character `& amp;` entity. For more information, refer to the [w3.org article](https://www.w3.org/TR/REC-xml/#syntax).
|
||||
|
||||
Any other HTML markup tags will be ignored during the processing of the report. If the HTML represented by the expression in the HtmlTextBox is badly formatted, the HtmlTextBox will throw an exception. Note that all HTML tags are case-insensitive.
|
||||
Any other HTML markup tags will be ignored during the processing of the report. If the HTML represented by the expression in the HtmlTextBox is badly formatted, the HtmlTextBox will throw an exception. Note that all HTML tags are case-insensitive.
|
||||
|
||||
The HtmlTextBox supports the following CSS attributes for styling its text:
|
||||
|
||||
|
|
|
|||
|
|
@ -11,9 +11,9 @@ position: 0
|
|||
|
||||
# HtmlTextBox Overview
|
||||
|
||||
The HtmlTextBox report item enables you to insert HTML-formatted text into a report.
|
||||
The HtmlTextBox report item enables you to insert HTML-formatted text into a report.
|
||||
|
||||
You can specify the HTML value at design time either through a WYSIWYG editor or through an expression editor, or retrieve it from a data source by using any simple or complex expression that evaluates to correctly formatted HTML.
|
||||
You can specify the HTML value at design time either through a WYSIWYG editor or through an expression editor, or retrieve it from a data source by using any simple or complex expression that evaluates to correctly formatted HTML.
|
||||
|
||||
|Design View of the HtmlTextBox Editor|
|
||||
|:---:|
|
||||
|
|
@ -23,7 +23,7 @@ You can specify the HTML value at design time either through a WYSIWYG editor o
|
|||
|
||||
* [XHTML validation]({%slug telerikreporting/designing-reports/report-structure/htmltextbox/xhtml-validation%})—The HtmlTextBox allows you to validate its defined content as valid XHTML.
|
||||
* [Formatting with the Telerik AJAX Editor]({%slug telerikreporting/designing-reports/report-structure/htmltextbox/using-html-from-telerik-radeditor%})—You can filter the HTML tags or CSS attributes that are not supported by the HtmlTextBox by using the Telerik UI for ASP.NET AJAX Editor.
|
||||
* [Editing]({%slug htmltextbox_editing%})—The HtmlTextBox supports data-driven inline fields which you can edit in place or through a design-time editor.
|
||||
* [Editing]({%slug htmltextbox_editing%})—The HtmlTextBox supports data-driven inline fields which you can edit in place or through a design-time editor.
|
||||
* [Styling and formatting]({%slug htmltextbox_formatting_and_styling%})—The HtmlTextBox enables you to control the presentation style of its text through the supported CSS attributes and HTML tags.
|
||||
* [Growing and shrinking]({%slug htmltextbox_grow_and_shrink%})—You can accommodate the content of the HtmlTextBox by allowing it to grow or shrink correspondingly.
|
||||
* [Embedded expressions]({%slug htmltextbox_embedded_expressions%})—With the HtmlTextBox, you can create a mail-merge functionality or a template for the text in your report.
|
||||
|
|
@ -33,7 +33,7 @@ You can specify the HTML value at design time either through a WYSIWYG editor o
|
|||
* [Getting Started with the HtmlTextBox Report Item]({%slug barcode_item_get_started%})
|
||||
* [(KB) Anchor Tags vs. Hyperlink Actions in the HtmlTextBox]({%slug htmltextbox-with-anchor-tag-vs-hyperlink-action%})
|
||||
* [(KB) Error while Parsing EntityName]({%slug htmltextbox-an-error-occurred-while-parsing-entityname%})
|
||||
* [(w3.org) Full List of Special Entities](http://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent)
|
||||
* [(w3.org) Full List of Special Entities](https://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent)
|
||||
* [Demo Page for Telerik Reporting](https://demos.telerik.com/reporting)
|
||||
* [Knowledge Base Section](/knowledge-base)
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ position: 7
|
|||
|
||||
The HtmlTextBox supports text formatting options, such as a subset of HTML tags and CSS attributes, which are available only for styling labels and headers. Therefore, to avoid exceptions, you have to filter the unsupported HTML tags or CSS attributes.
|
||||
|
||||
This article outlines how to accomplish this scenario when the HTML data entry tool is the [Telerik UI for ASP.NET AJAX Editor](http://www.telerik.com/products/aspnet-ajax/editor.aspx).
|
||||
This article outlines how to accomplish this scenario when the HTML data entry tool is the [Telerik UI for ASP.NET AJAX Editor](https://www.telerik.com/products/aspnet-ajax/editor.aspx).
|
||||
|
||||
Before you start, note the following considerations:
|
||||
|
||||
|
|
@ -96,7 +96,6 @@ RadEditor1.DisableFilter(Telerik.Web.UI.EditorFilters.ConvertFontToSpan)
|
|||
|
||||
|
||||
1. Strip the HTML formatting from the pasted content, because users may paste content that is badly formatted and thus break the HtmlTextBox and its PDF export feature. To achieve this behavior, set the `StripFormattingOptions` property to `All` or to `AllExceptNewLines`.
|
||||
|
||||
1. Use the following custom content filter, which will remove unsupported HTML tags.
|
||||
|
||||
The supported tags are `FONT`, `STRONG`, `B`, `EM`, `I`, `U`, `A`, `OL`, `UL`, `SUB`, `SUP`, `LI`, `DIV`, `SPAN`, `P`, `BR`, `CENTER`.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ position: 4
|
|||
|
||||
In this article, you will learn how to create a Map report item with a BarChart series.
|
||||
|
||||
The suggested scenario will demonstrate how to create a Map which will present the [countries with the most medals won in Olympic Games](http://en.wikipedia.org/wiki/All-time_Olympic_Games_medal_table) divided by their continental [Association of National Olympic Committees](http://www.olympic.org/ioc-governance-national-olympic-committees). The example will also add some interactivity to the report, enabling the user to choose which countries will be displayed on the Map, highlighting the currently selected country, and displaying an additional chart with detailed information about it. The suggested implementation uses the [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) and does not require the writing of any code.
|
||||
The suggested scenario will demonstrate how to create a Map which will present the [countries with the most medals won in Olympic Games](https://en.wikipedia.org/wiki/All-time_Olympic_Games_medal_table) divided by their continental [Association of National Olympic Committees](https://olympics.com/ioc/national-olympic-committees). The example will also add some interactivity to the report, enabling the user to choose which countries will be displayed on the Map, highlighting the currently selected country, and displaying an additional chart with detailed information about it. The suggested implementation uses the [Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) and does not require the writing of any code.
|
||||
|
||||
The suggested implementation corresponds to the sample `OlympicMedalsByNationalTeams.trdp` report definition that may be found in the installation folder of the Telerik Reporting product. By default, this is `C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer\Examples`.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ This article demonstrates how to add a Choropleth map to your report by using th
|
|||
|
||||
The suggested approach will create and set up a Choropleth map that will show the world population for each country and coloring its area depending on the population density value.
|
||||
|
||||
You will use a [CSV Data Source]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/data-source-wizards/csvdatasource-wizard%}) for the analytical data and an [ESRI Shapefile](http://en.wikipedia.org/wiki/Shapefile) for the spatial data.
|
||||
You will use a [CSV Data Source]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/data-source-wizards/csvdatasource-wizard%}) for the analytical data and an [ESRI Shapefile](https://en.wikipedia.org/wiki/Shapefile) for the spatial data.
|
||||
|
||||
The analytical data will be obtained from the [List of sovereign states and dependent territories by population density](http://en.wikipedia.org/wiki/List_of_sovereign_states_and_dependent_territories_by_population_density) Wikipedia article.
|
||||
The analytical data will be obtained from the [List of sovereign states and dependent territories by population density](https://en.wikipedia.org/wiki/List_of_countries_and_dependencies_by_population_density) Wikipedia article.
|
||||
|
||||
## 1. Start the Map Wizard
|
||||
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ Identical to the Pie chart type of the Graph, the Column map type presents analy
|
|||
|
||||
The [Choropleth map type](https://en.wikipedia.org/wiki/Choropleth_map) is a thematic map that uses graded color differences to display a measure over predefined regions or areas, and is one of the most popular ways to visualize how a measure varies across a geographic area.
|
||||
|
||||
The Choropleth item is basically a [Map item]({%slug telerikreporting/designing-reports/report-structure/map/structure/overview%}) with a special kind of series and groups. To create a Choropleth map, you don't have to configure a [location provider]({%slug telerikreporting/designing-reports/report-structure/map/structure/location-providers%}) or use a [`GeoLocationMapGroup`](/api/Telerik.Reporting.GeoLocationMapGroup) to obtain the coordinates of the data points. Instead, the Choropleth uses a [`ShapeMapSeries`](/api/Telerik.Reporting.ShapeMapSeries) instance whose major distinction from the other Map series is that they define the source which will be used to provide the spatial data. This source can be either a string, formatted in compliance with the [Well-known text or Well-known binary](http://en.wikipedia.org/wiki/Well-known_text) standards, or an [ESRI Shapefile](https://en.wikipedia.org/wiki/Shapefile).
|
||||
The Choropleth item is basically a [Map item]({%slug telerikreporting/designing-reports/report-structure/map/structure/overview%}) with a special kind of series and groups. To create a Choropleth map, you don't have to configure a [location provider]({%slug telerikreporting/designing-reports/report-structure/map/structure/location-providers%}) or use a [`GeoLocationMapGroup`](/api/Telerik.Reporting.GeoLocationMapGroup) to obtain the coordinates of the data points. Instead, the Choropleth uses a [`ShapeMapSeries`](/api/Telerik.Reporting.ShapeMapSeries) instance whose major distinction from the other Map series is that they define the source which will be used to provide the spatial data. This source can be either a string, formatted in compliance with the [Well-known text or Well-known binary](https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry) standards, or an [ESRI Shapefile](https://en.wikipedia.org/wiki/Shapefile).
|
||||
|
||||
To improve the appearance, the Map item can define a [tile provider]({%slug telerikreporting/designing-reports/report-structure/map/structure/tile-providers%}) which will draw an image of the requested Map extent as a background layer onto the plot area.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,11 +20,11 @@ The map supports the following location providers:
|
|||
|
||||
The query arguments order is of a huge significance. In the example above, if you switch the query arguments to **Austria, Vienna**, the service will return no results.
|
||||
|
||||
* [`MapQuestLocationProvider`](/api/Telerik.Reporting.MapQuestLocationProvider)—Uses the [MapQuest Geocoding API](http://developer.mapquest.com/web/products/dev-services/geocoding-ws) geocoding service to provide a single-line address and receive potential geographical coordinates of the geocoded location.
|
||||
* [`MapQuestLocationProvider`](/api/Telerik.Reporting.MapQuestLocationProvider)—Uses the [MapQuest Geocoding API](https://developer.mapquest.com/documentation/geocoding-api/) geocoding service to provide a single-line address and receive potential geographical coordinates of the geocoded location.
|
||||
|
||||
The query arguments order is of a huge significance. In the example above, if you switch the query arguments to **Austria, Vienna**, the service will return **Vienna, Dooly County, GA, USA**.
|
||||
|
||||
* [`BingLocationProvider`](/api/Telerik.Reporting.BingLocationProvider)—Uses the [Bing™ Maps Locations API](http://msdn.microsoft.com/en-us/library/ff701715.aspx) to get location information about the requested address.
|
||||
* [`BingLocationProvider`](/api/Telerik.Reporting.BingLocationProvider)—Uses the [Bing™ Maps Locations API](https://learn.microsoft.com/en-us/bingmaps/rest-services/locations/) to get location information about the requested address.
|
||||
|
||||
## See Also
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,6 @@ Data point labels are used to display the exact value represented by a data poin
|
|||
Series represent a number of data points that show individual measurements. Depending on the groups they use and the data points they display, the series in the Map report item can be divided into two major categories.
|
||||
|
||||
* [`LocationMapSeries`](/api/Telerik.Reporting.LocationMapSeries)—To determine its data points position on the map, this category uses [`GeoLocationMapGroup`](/api/Telerik.Reporting.GeoLocationMapGroup) to obtain a set of latitude and longitude coordinates, or to query the defined [location provider]({%slug telerikreporting/designing-reports/report-structure/map/structure/location-providers%}). Location map series are the Point, Pie, and Column map types because they present similar data points each one on a single location on the map.
|
||||
|
||||
* [`ShapeMapSeries`](/api/Telerik.Reporting.ShapeMapSeries)—This category uses a set of coordinates to determine the shape of the data point itself. In this case, the engine does not use a `LocationProvider` or a `GeoLocationMapGroup` because the data points are not determined by a single location on the map surface.
|
||||
|
||||
The Map series can share existing `GeoLocation`, `ShapeMap`, and `Series` groups.
|
||||
|
|
@ -57,7 +56,7 @@ The Map legend is a collection of legend items that are used to distinguish the
|
|||
|
||||
## Scale
|
||||
|
||||
The [`MapScaleLegend`](/api/Telerik.Reporting.MapScaleLegend) shows the scale of the current map extent measured in the middle between its minimum and maximum latitude. The scale is calculated by using the [Haversine formula](http://en.wikipedia.org/wiki/Haversine_formula) which assumes that the Earth is a perfect sphere.
|
||||
The [`MapScaleLegend`](/api/Telerik.Reporting.MapScaleLegend) shows the scale of the current map extent measured in the middle between its minimum and maximum latitude. The scale is calculated by using the [Haversine formula](https://en.wikipedia.org/wiki/Haversine_formula) which assumes that the Earth is a perfect sphere.
|
||||
|
||||
### Formatting the Scale Legend
|
||||
|
||||
|
|
|
|||
|
|
@ -18,31 +18,31 @@ The [Map](/api/Telerik.Reporting.Map) supports the [`BingMapsTileProvider`](/api
|
|||
|
||||
## Bing Maps Tile Provider
|
||||
|
||||
The [`BingMapsTileProvider`](/api/Telerik.Reporting.BingMapsTileProvider) uses the [Bing Maps REST Services](http://msdn.microsoft.com/en-us/library/ff701713.aspx) to request metadata information that is needed to resolve the tile requests URLs, zoom levels, tile sizes and attribution information such as the text or logo that will be displayed on the map. The user doesn't need to provide any server URL, subdomains, or another tiles-related information because it is retrieved automatically from the imagery metadata according to the desired imagery set.
|
||||
The [`BingMapsTileProvider`](/api/Telerik.Reporting.BingMapsTileProvider) uses the [Bing Maps REST Services](https://learn.microsoft.com/en-us/bingmaps/rest-services/) to request metadata information that is needed to resolve the tile requests URLs, zoom levels, tile sizes and attribution information such as the text or logo that will be displayed on the map. The user doesn't need to provide any server URL, subdomains, or another tiles-related information because it is retrieved automatically from the imagery metadata according to the desired imagery set.
|
||||
|
||||
The `BingMapsTileProvider` provides the **Aerial**, **Road**, and **Aerial with Labels** (an Aerial imagery with a road overlay) types of imagery sets that are mapped to the predefined values of the [`ImagerySet`](/api/Telerik.Reporting.ImagerySet) property (`Aerial`, `Road`, `Hybrid`). Changing the imagery set causes the `BingTileProvider` to request images from a different tile set, thus changing the look of the map. The tile server requires a Bing Maps Key client token for authentication which you can obtain from the [Bing Maps website](http://www.microsoft.com/maps/create-a-bing-maps-key.aspx).
|
||||
The `BingMapsTileProvider` provides the **Aerial**, **Road**, and **Aerial with Labels** (an Aerial imagery with a road overlay) types of imagery sets that are mapped to the predefined values of the [`ImagerySet`](/api/Telerik.Reporting.ImagerySet) property (`Aerial`, `Road`, `Hybrid`). Changing the imagery set causes the `BingTileProvider` to request images from a different tile set, thus changing the look of the map. The tile server requires a Bing Maps Key client token for authentication which you can obtain from the [Bing Maps website](https://www.microsoft.com/en-us/maps/create-a-bing-maps-key).
|
||||
|
||||
## Generic Tile Provider
|
||||
|
||||
The [`GenericTileProvider`](/api/Telerik.Reporting.GenericTileProvider) requires the user to manually provide a template to the server URL, the subdomain names if needed, the application user agent, the attribution text, and the URL.
|
||||
|
||||
* The `GenericTileProvider` is designed in compliance with the [Web Map Tile Service](http://en.wikipedia.org/wiki/Web_Map_Tile_Service) protocol that defines a standard way for requesting and receiving pre-rendered map tiles. The protocol works with the most common 256x256px tile size and uses popular mathematical algorithms to calculate and process the results.
|
||||
* You can set up the `GenericTileProvider` to show tiles from other tile providers such as [OpenStreetMap](http://www.openstreetmap.org), [HERE Maps](http://here.com/), [Yandex Maps](http://maps.yandex.com) as they comply with the the [WMTS](http://en.wikipedia.org/wiki/Web_Map_Tile_Service) protocol.
|
||||
* The provider requires a [`UrlTemplate`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlTemplate) and [`UrlSubdomains`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlSubdomains) to construct the tile requests URL. If the combination of the `UrlTemplate` and `UrlSubdomains` result in an invalid URI or a tile cannot be retrieved from the tile server, the Map will display a substitute tile containing the exception message. The `UrlTemplate` includes the `{subdomain}`, `{zoom}`, `{x}`, and `{y}` tags, and acquires the `http://{subdomain}.tile.openstreetmap.org/{zoom}/{x}/{y}.png"` format.
|
||||
* The `GenericTileProvider` is designed in compliance with the [Web Map Tile Service](https://en.wikipedia.org/wiki/Web_Map_Tile_Service) protocol that defines a standard way for requesting and receiving pre-rendered map tiles. The protocol works with the most common 256x256px tile size and uses popular mathematical algorithms to calculate and process the results.
|
||||
* You can set up the `GenericTileProvider` to show tiles from other tile providers such as [OpenStreetMap](https://www.openstreetmap.org), [HERE Maps](https://www.here.com/), [Yandex Maps](https://yandex.com/maps/) as they comply with the the [WMTS](https://en.wikipedia.org/wiki/Web_Map_Tile_Service) protocol.
|
||||
* The provider requires a [`UrlTemplate`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlTemplate) and [`UrlSubdomains`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlSubdomains) to construct the tile requests URL. If the combination of the `UrlTemplate` and `UrlSubdomains` result in an invalid URI or a tile cannot be retrieved from the tile server, the Map will display a substitute tile containing the exception message. The `UrlTemplate` includes the `{subdomain}`, `{zoom}`, `{x}`, and `{y}` tags, and acquires the `https://{subdomain}.tile.openstreetmap.org/{zoom}/{x}/{y}.png"` format.
|
||||
* The format tags are case-insensitive and can be placed in any order. The mandatory ones are `{zoom}`, `{x}`, and `{y}`, because they uniquely define a tile position on a tile set. The `{subdomain}` tag marks the place where a subdomain from the [`UrlSubdomains`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlSubdomains) collection will be placed.
|
||||
|
||||
* `{subdomain}` is not mandatory, since the selected tile provider may not offer more than one subdomain.
|
||||
* The `{zoom}` tag will be replaced by the calculated zoom level (level of details) of the current tile set. The level of details depends on the map extent and on the map control size. When the processing engine calculates the appropriate zoom level, its value will replace the `{zoom}` tag.
|
||||
* The `{x}` and `{y}` tags are used as a placeholders for the tile position. Before starting to fetch the tiles for the requested map extent, the processing engine will calculate the zoom level and the coordinates of the tiles used to display the extent. When constructing the request, the `{x}` and `{y}` tags will be replaced by the calculated __X__ and __Y__ tile coordinates.
|
||||
|
||||
* The image extension (`.jpg` in the example above) is not mandatory and the provider defines whether to include it or not. [Some tile providers](http://maptile.maps.svc.ovi.com/maptiler/maptile/newest/normal.day/2/2/1/256/png8) do not require an image extension to be requested, while [others](http://otile2.mqcdn.com/tiles/1.0.0/map/2/2/1.gif) return the tiles in the same format, regardless of the requested extension.
|
||||
* The [`UrlSubdomains`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlSubdomains) property is a collection of strings, representing the subdomains that will be used to construct the tile URLs. For example, the [OpenStreetMap](http://www.openstreetmap.com/) subdomains are `a`, `b`, and `c`. When the processing engine calculates how many tiles will be needed for the requested map extent, it will distribute the web requests evenly among the subdomains for an additional performance gain.
|
||||
* The image extension (`.jpg` in the example above) is not mandatory and the provider defines whether to include it or not. [Some tile providers](https://maptile.maps.svc.ovi.com/maptiler/maptile/newest/normal.day/2/2/1/256/png8) do not require an image extension to be requested, while [others](http://otile2.mqcdn.com/tiles/1.0.0/map/2/2/1.gif) return the tiles in the same format, regardless of the requested extension.
|
||||
* The [`UrlSubdomains`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlSubdomains) property is a collection of strings, representing the subdomains that will be used to construct the tile URLs. For example, the [OpenStreetMap](https://www.openstreetmap.org/) subdomains are `a`, `b`, and `c`. When the processing engine calculates how many tiles will be needed for the requested map extent, it will distribute the web requests evenly among the subdomains for an additional performance gain.
|
||||
* In some scenarios it's required to set a value of the `UserAgent` web request header, which is sent to the tile providing web services. In this case, the [`UserAgent`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UserAgent) property must be populated with a constant string or an expression that will be evaluated during the report processing. The value of this property will be set as a value of the `UserAgent` web request header. Initially, the value of the `UserAgent` property will be set to a newly generated GUID, but it has to be replaced with a correct value according to the usage policy of the tile provider.
|
||||
* The users also have to provide [`Attribution`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_Attribution) text and a [`LogoUrl`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_LogoUrl) that will be used to display an attribution information on the map. The [`Attribution`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_Attribution) property must be manually set according to the [usage policy](http://wiki.openstreetmap.org/wiki/Legal_FAQ) of the tile provider. This text will be displayed in the lower right corner of the map area. The [`LogoUrl`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_LogoUrl) property denotes the URL used to download the tile provider [logo](http://wiki.openstreetmap.org/w/images/thumb/7/79/Public-images-osm_logo.svg/32px-Public-images-osm_logo.svg.png), if required by the usage policy of the provider. If the URL points to a valid image, it will be displayed in the lower left corner of the map area.
|
||||
* The users also have to provide [`Attribution`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_Attribution) text and a [`LogoUrl`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_LogoUrl) that will be used to display an attribution information on the map. The [`Attribution`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_Attribution) property must be manually set according to the [usage policy](https://wiki.openstreetmap.org/wiki/Legal_FAQ) of the tile provider. This text will be displayed in the lower right corner of the map area. The [`LogoUrl`](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_LogoUrl) property denotes the URL used to download the tile provider [logo](https://wiki.openstreetmap.org/w/images/thumb/7/79/Public-images-osm_logo.svg/32px-Public-images-osm_logo.svg.png), if required by the usage policy of the provider. If the URL points to a valid image, it will be displayed in the lower left corner of the map area.
|
||||
|
||||
## (Obsolete) Map Quest Tile Provider
|
||||
|
||||
The obsolete [`MapQuestTileProvider`](/api/Telerik.Reporting.MapQuestTileProvider) uses the [`MapQuest`](http://www.mapquest.com/) tile servers that provides the tiles in the **OpenStreetMap Tiles** and the **MapQuest Open Aerial Tiles** imagery sets.
|
||||
The obsolete [`MapQuestTileProvider`](/api/Telerik.Reporting.MapQuestTileProvider) uses the [`MapQuest`](https://www.mapquest.com/) tile servers that provides the tiles in the **OpenStreetMap Tiles** and the **MapQuest Open Aerial Tiles** imagery sets.
|
||||
|
||||
The tile server does not require a Client Token for authentication. The [`MapQuestTileProvider`](/api/Telerik.Reporting.MapQuestTileProvider) is substituted by the [`GenericTileProvider`](/api/Telerik.Reporting.GenericTileProvider) to provide more control over the tile provider settings and to avoid the pre-setup provider configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ To set an expression as a PictureBox value in the Report Designer:
|
|||
|
||||
To bind an image data to a PictureBox when using a Report Designer is a straight-forward process. You need to connect to a data source and drag the image field from the [**Data Explorer**]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/data-explorer%}) window to your report. As a result, the report designer tool will associate each field based on its data type.
|
||||
|
||||
Alternatively, you can drag a PictureBox item to the design surface and use an expression to set its `Value` property to an existing field from the data source. The type of the `PictureBox.Value` property is [`Object`](https://learn.microsoft.com/en-us/dotnet/api/system.object) which allows for versatile data binding and you do not have to directly bind to a database field with an image column.
|
||||
Alternatively, you can drag a PictureBox item to the design surface and use an expression to set its `Value` property to an existing field from the data source. The type of the `PictureBox.Value` property is [`Object`](https://learn.microsoft.com/en-us/dotnet/api/system.object) which allows for versatile data binding and you do not have to directly bind to a database field with an image column.
|
||||
|
||||
The `Value` property accepts objects of type [`Image`](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.image), byte array and strings. The string can be either of the following:
|
||||
|
||||
|
|
@ -67,7 +67,7 @@ The `Value` property accepts objects of type [`Image`](https://learn.microsoft.c
|
|||
|
||||
### Binding to Binary Images
|
||||
|
||||
You can directly assign a reference to an [`Image`](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.image) to the `Value` property of a PictureBox.
|
||||
You can directly assign a reference to an [`Image`](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.image) to the `Value` property of a PictureBox.
|
||||
|
||||
````C#
|
||||
using System.Drawing;
|
||||
|
|
@ -84,7 +84,7 @@ Dim image2 As Image = Image.FromStream(imageStream)
|
|||
Me.PictureBox2.Value = image2
|
||||
````
|
||||
|
||||
While in design-time within the [Visual Studio Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/overview%}), if you click the ellipsis of the `Value` property, a dialog appears for you to choose the desired image. After you select the image, the Designer will automatically store it in the resources file for the report (`.resx`) and add a line of code to the `InitializeComponent` method that obtains a reference to the image stored in the resources and assigns it to the `Value` of the PictureBox:
|
||||
While in design-time within the [Visual Studio Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/overview%}), if you click the ellipsis of the `Value` property, a dialog appears for you to choose the desired image. After you select the image, the Designer will automatically store it in the resources file for the report (`.resx`) and add a line of code to the `InitializeComponent` method that obtains a reference to the image stored in the resources and assigns it to the `Value` of the PictureBox:
|
||||
|
||||
````C#
|
||||
this.pictureBox1.Value = ((object)(resources.GetObject("pictureBox1.Value")));
|
||||
|
|
@ -107,14 +107,12 @@ End Function
|
|||
````
|
||||
|
||||
|
||||
### Binding to Expressions, URIs, Base64, and SVG
|
||||
### Binding to Expressions, URIs, Base64, and SVG
|
||||
|
||||
Alternatively, you can assign a string value to the `Value` property. This string value can be any of the following:
|
||||
|
||||
* An [item binding expression]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/using-expressions/overview%})—When binding to a data field with an expression, the Value property will accept both `binary` and `string` data fields.
|
||||
|
||||
* A [URI](http://en.wikipedia.org/wiki/URI)—The `Value` property supports both absolute and relative URIs.
|
||||
|
||||
* An [item binding expression]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/using-expressions/overview%})—When binding to a data field with an expression, the Value property will accept both `binary` and `string` data fields.
|
||||
* A [URI](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier)—The `Value` property supports both absolute and relative URIs.
|
||||
* A string representing a Base64-encoded image or a valid SVG markup—For optimization, the engine initially checks the length of the string value.
|
||||
|
||||
If it is less than 80 characters, the value is considered to be an URI. Otherwise, the string is tested whether it is SVG markup (if its first 256 characters contain `<svg`) or a Base64-encoded string.
|
||||
|
|
@ -125,19 +123,19 @@ To sum it up, the data source column of the PictureBox can store the image objec
|
|||
|
||||
````C#
|
||||
this.pictureBox1.Value = "=Fields.MyImageBinary";//a binary data column
|
||||
this.pictureBox2.Value = "=Fields.MyImageURI";//a data column containing an URI
|
||||
this.pictureBox2.Value = "=Fields.MyImageURI";//a data column containing an URI
|
||||
this.pictureBox3.Value = @"C:\MyPictures\MyPicture.png";//absolute file path to a PNG file
|
||||
this.pictureBox4.Value = @"C:\MyPictures\MySVGImage.svg";//absolute file path to an SVG file
|
||||
this.pictureBox5.Value = @".\images\MyPicture.png";//relative path
|
||||
this.pictureBox6.Value = "http://www.mysite.com/images/img1.gif";//absolute URL
|
||||
this.pictureBox6.Value = "https://www.mysite.com/images/img1.gif";//absolute URL
|
||||
````
|
||||
````VB.NET
|
||||
Me.PictureBox1.Value = "=Fields.MyImageBinary" 'a binary data column
|
||||
Me.PictureBox2.Value = "=Fields.MyImageURI" 'a data column containing an URI
|
||||
Me.PictureBox2.Value = "=Fields.MyImageURI" 'a data column containing an URI
|
||||
Me.PictureBox3.Value = "C:\MyPictures\MyPicture.png" 'absolute file path to a PNG image
|
||||
Me.PictureBox4.Value = "C:\MyPictures\MySVGImage.svg" 'absolute file path to an SVG file
|
||||
Me.PictureBox5.Value = ".\images\MyPicture.png" 'relative path
|
||||
Me.PictureBox6.Value = "http://www.mysite.com/images/img1.gif" 'absolute URL
|
||||
Me.PictureBox6.Value = "https://www.mysite.com/images/img1.gif" 'absolute URL
|
||||
````
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ The following image shows a TextBox with an activated in-place editor.
|
|||
|
||||
## Using the Expression Editor
|
||||
|
||||
For more information about how to use the Expression editor, refer to the article on the [**Edit Expression** dialog]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/edit-expression-dialog%}). Note that when pressing the `Enter` key inserts a new line in the expression. To insert a new line in the string resulting from the evaluated expression, enclose the new line within double quotes (`"..."`).
|
||||
For more information about how to use the Expression editor, refer to the article on the [**Edit Expression** dialog]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/edit-expression-dialog%}). Note that when pressing the `Enter` key inserts a new line in the expression. To insert a new line in the string resulting from the evaluated expression, enclose the new line within double quotes (`"..."`).
|
||||
|
||||
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ The TextBox report item supports [embedded expressions]({%slug telerikreporting/
|
|||
Before you apply a TextBox format, consider the following:
|
||||
|
||||
* By default, numbers are formatted to reflect the cultural settings on the client computer. To specify how numbers are displayed and provide consistent formatting regardless of where the person who is viewing the report is located, use formatting strings.
|
||||
* The formats provided on the **Number** page are a subset of the .NET Framework standard numeric format strings. To format a number or a date by using a custom format that is not shown in the dialog box, use any number or date .NET Framework format strings. For more information about custom format strings, refer to the [MSDN Formatting Types](http://msdn.microsoft.com/en-us/library/fbxft59x%28VS.95%29.aspx) topic.
|
||||
* The formats provided on the **Number** page are a subset of the .NET Framework standard numeric format strings. To format a number or a date by using a custom format that is not shown in the dialog box, use any number or date .NET Framework format strings. For more information about custom format strings, refer to the article [Formatting Types](https://learn.microsoft.com/en-us/dotnet/standard/base-types/formatting-types) topic.
|
||||
* If you specify a custom format string, it will prevail over the default settings that are culture-specific. For example, if you set a custom format string of `#,###` to render 1234 as `1,234`, users in different parts of the world may interpret it in different ways. Before specifying a custom format, consider how the chosen format will affect users of different cultures viewing the report.
|
||||
* If you specify an invalid format string, it will override the actual `Value`.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ published: True
|
|||
position: 4
|
||||
previous_url: /designing-reports-considerations-excel
|
||||
---
|
||||
|
||||
<style>
|
||||
table th:first-of-type {
|
||||
width: 20%;
|
||||
|
|
@ -24,9 +25,9 @@ __Telerik Reporting__ produces Excel files in:
|
|||
* Microsoft Excel 2007 and above (OpenXML 2.0). This rendering extension requires [Third-Party Dependencies]({%slug telerikreporting/using-reports-in-applications/third-party-dependencies%}).
|
||||
* Microsoft Excel 97-2003 (BIFF, v.8)
|
||||
|
||||
Telerik Reporting does not rely on Microsoft Office being installed in order to export to both formats. __Microsoft Excel 97-2003__ files can be opened by Microsoft Excel 97 for Windows and later.
|
||||
Telerik Reporting does not rely on Microsoft Office being installed in order to export to both formats. __Microsoft Excel 97-2003__ files can be opened by Microsoft Excel 97 for Windows and later.
|
||||
|
||||
__Microsoft Excel 2007__ files can be opened by Microsoft Excel 2007 for Windows and later and has the following advantages over __Microsoft Excel 97-2003__ :
|
||||
__Microsoft Excel 2007__ files can be opened by Microsoft Excel 2007 for Windows and later and has the following advantages over __Microsoft Excel 97-2003__ :
|
||||
|
||||
* Works in Medium Trust.
|
||||
* Supports up to 16 million colors.
|
||||
|
|
@ -47,7 +48,7 @@ The Excel Rendering Extensions tries to reproduce as much of the original report
|
|||
|
||||
|
||||
|
||||
* When you use the CanGrow and CanShrink properties, the Rendering Engine will utilize the AutoFit functionality of Excel. That means that cell content will resize according to Excel behavior which might not produce the expected result. Furthermore, AutoFit is applied by Excel only for horizontal text, so if you have rotated text (at an angle different than zero), the CanGrow and CanShrink properties might not behave as expected. Rotated text is realized via Excel's built-in cell rotation settings.
|
||||
* When you use the CanGrow and CanShrink properties, the Rendering Engine will utilize the AutoFit functionality of Excel. That means that cell content will resize according to Excel behavior which might not produce the expected result. Furthermore, AutoFit is applied by Excel only for horizontal text, so if you have rotated text (at an angle different than zero), the CanGrow and CanShrink properties might not behave as expected. Rotated text is realized via Excel's built-in cell rotation settings.
|
||||
* Multi-column reports are not supported.
|
||||
|
||||
## Page Headers and Footers
|
||||
|
|
@ -60,7 +61,7 @@ With default configuration (__UseNativePageHeader__ is False and __UseNativePage
|
|||
|
||||
The native Excel page header/footer is not displayed on the Excel worksheet in Normal view - it is displayed only in Page Layout view and on the printed pages. For more information see [Headers and footers in a worksheet](https://support.office.com/en-us/article/Headers-and-footers-in-a-worksheet-cae2a88c-64a7-42ab-96a4-28d2fc16ad31).
|
||||
|
||||
>caution The __PageNumber__ and __PageCount__ global objects' behavior depends on the __UseNativePageHeader__ and __UseNativePageFooter__ configuration. Since the report rendered to Excel is not in a page-oriented format and is contained in a single worksheet (regarded as a single page) __PageNumber__ and __PageCount__ will always return a value of 1. However, if you intend to print the Excel document and would like to let Excel handle the page numbering instead, you can do so by setting both __UseNativePageHeader__ and __UseNativePageFooter__ to __True__. This configuration will force the Reporting engine to use the native Excel page number and page count tokens, instead of the default value of 1, so the page number and count are correct when the document is printed in Excel. When the native Excel page tokens are used, any arithmetic operations on the PageNumber/PageCount are not supported. Since the PageNumber() and PageCount() functions use arithmetic operations internally, they are also not supported in the native page header/page footer sections.
|
||||
>caution The __PageNumber__ and __PageCount__ global objects' behavior depends on the __UseNativePageHeader__ and __UseNativePageFooter__ configuration. Since the report rendered to Excel is not in a page-oriented format and is contained in a single worksheet (regarded as a single page) __PageNumber__ and __PageCount__ will always return a value of 1. However, if you intend to print the Excel document and would like to let Excel handle the page numbering instead, you can do so by setting both __UseNativePageHeader__ and __UseNativePageFooter__ to __True__. This configuration will force the Reporting engine to use the native Excel page number and page count tokens, instead of the default value of 1, so the page number and count are correct when the document is printed in Excel. When the native Excel page tokens are used, any arithmetic operations on the PageNumber/PageCount are not supported. Since the PageNumber() and PageCount() functions use arithmetic operations internally, they are also not supported in the native page header/page footer sections.
|
||||
|
||||
## ReportBook
|
||||
|
||||
|
|
@ -127,7 +128,7 @@ The following standard paper kinds are supported:
|
|||
* Number11Envelope (4.5” x 10.375”)
|
||||
* Number12Envelope (4.75” x 11”)
|
||||
* Number14Envelope (5” x 11.5”)
|
||||
* DSheet (22” x 34”)
|
||||
* DSheet (22” x 34”)
|
||||
* ESheet (34” x 44”)
|
||||
* MonarchEnvelope (3.875” x 7.5”)
|
||||
* PersonalEnvelope (3.625” x 6.5”)
|
||||
|
|
@ -165,7 +166,7 @@ To preserve the result from previewing the rendered document, formats are saved
|
|||
* F (Full date/time pattern with long time)
|
||||
* g (General date/time pattern with short time)
|
||||
* G (General date/time pattern with long time)
|
||||
* M or m (Month day pattern)
|
||||
* M or m (Month day pattern)
|
||||
* R or r (RFC1123 pattern)
|
||||
* s (Sortable date/time pattern; conforms to ISO 8601)
|
||||
* u (Universal sortable date/time pattern)
|
||||
|
|
@ -187,7 +188,7 @@ Excel places limitations on exported reports due to the format capabilities. The
|
|||
* TextBoxes are rendered within one Excel cell. Font size, font face, decoration, font style and text/vertical align are the only formatting that is supported on individual text within an Excel cell.
|
||||
* Telerik Reporting expressions are not converted to Excel formulas. TextBox values that are expressions are evaluated during report processing and the result is exported as content of Excel cell.
|
||||
* Excel does not support background images for individual cells, so Background images for report items (including Report) are ignored.
|
||||
* Excel native page headers and footers support a maximum of 255 characters including [Formatting and VBA Codes for Headers and Footers](http://msdn.microsoft.com/en-us/library/bb225426.aspx). The rendering extension truncates the string at 255 characters.
|
||||
* Excel native page headers and footers support a maximum of 255 characters including [Formatting and VBA Codes for Headers and Footers](https://learn.microsoft.com/en-us/previous-versions/office/developer/office-2007/bb225426(v=office.12)). The rendering extension truncates the string at 255 characters.
|
||||
* Excel does not support Watermarks.
|
||||
* Underlining justified text will only underline the words and not the spaces between them.
|
||||
* Table of contents is not supported.
|
||||
|
|
|
|||
|
|
@ -41,8 +41,8 @@ The legacy ASP.NET viewer renders tooltips on SVG elements using the `<title>` a
|
|||
|
||||
### Browsers and limitations
|
||||
|
||||
* Internet Explorer Quirks Mode is not supported, since it is based on Internet Explorer 5.5. For more details check the [Defining document compatibility](http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx) MSDN article.
|
||||
* Compatibility View for Internet Explorer is not supported, since it is based on Internet Explorer 7. For more details check the [Defining document compatibility](http://msdn.microsoft.com/en-us/library/cc288325(v=vs.85).aspx) MSDN article.
|
||||
* Internet Explorer Quirks Mode is not supported, since it is based on Internet Explorer 5.5. For more details check the [Defining document compatibility](https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/cc288325(v=vs.85)) MSDN article.
|
||||
* Compatibility View for Internet Explorer is not supported, since it is based on Internet Explorer 7. For more details check the [Defining document compatibility](https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/cc288325(v=vs.85)) MSDN article.
|
||||
* Internet Explorer has a limitation for the number of HTML elements that can be rendered on a single page. This limitation may prevent the displaying of reports with large amount of items rendered without page breaks. Displaying the report in Print preview will page the content.
|
||||
* Depending on the browser's layout engine fonts can be measured differently, which may lead to displaying clipped text in reports. The used in the reports fonts should be considered with the targeted browsers.
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ The legacy ASP.NET viewer renders tooltips on SVG elements using the `<title>` a
|
|||
|
||||
### Rendering
|
||||
|
||||
Reports can be output as MHTML (Web archive or "MIME Encapsulation of Aggregate HTML Documents") standard. MHTML is used for including resources in the same file as the HTML code. This is particularly useful when sending email because all resources, such as image and sound files, are included in a single file.
|
||||
Reports can be output as MHTML (Web archive or "MIME Encapsulation of Aggregate HTML Documents") standard. MHTML is used for including resources in the same file as the HTML code. This is particularly useful when sending email because all resources, such as image and sound files, are included in a single file.
|
||||
|
||||
The following rendering specifics apply to MHTML:
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Styles created in a report can be exported and then used in other reports. You c
|
|||
1. Open the report in design view.
|
||||
1. Select the __Report__ object.
|
||||
1. Click in the __StyleSheet__ property, and then click the ellipsis button to open the StyleRule Collection Editor.
|
||||
1. Select one or more of the styles in the Members box on the left. Use Windows keyboard combinations to select more than one style.
|
||||
1. Select one or more of the styles in the Members box on the left. Use Windows keyboard combinations to select more than one style.
|
||||
|
||||
|
||||
|
||||
|
|
@ -29,24 +29,24 @@ Styles created in a report can be exported and then used in other reports. You c
|
|||
|
||||
1. Open the report in design view.
|
||||
1. Select the __Report__ object.
|
||||
1. Click in the __ExternalStylesSheets__ property, and then click the ellipsis button to open the Collection Editor.
|
||||
1. Click the __New__ icon in the upper left corner of the Collection Editor window. This will open a __File Open__ dialog. You will be located in the current project's root directory.
|
||||
1. Browse to, and then select, the exported Style Sheet. Click __Open__. This action will return you to the Collection Editor window.
|
||||
1. Click in the __ExternalStylesSheets__ property, and then click the ellipsis button to open the Collection Editor.
|
||||
1. Click the __New__ icon in the upper left corner of the Collection Editor window. This will open a __File Open__ dialog. You will be located in the current project's root directory.
|
||||
1. Browse to, and then select, the exported Style Sheet. Click __Open__. This action will return you to the Collection Editor window.
|
||||
1. When you are finished adding Style Sheets, click __OK__.
|
||||
|
||||
Styles that are defined by __TypeSelectors__ or __AttributeSelectors__ will be automatically formatted. To use styles defined by __StyleSelectors__, change the __StyleName__ property of the desired report item to the appropriate style names that exist in the Style Sheets that you added.
|
||||
Styles that are defined by __TypeSelectors__ or __AttributeSelectors__ will be automatically formatted. To use styles defined by __StyleSelectors__, change the __StyleName__ property of the desired report item to the appropriate style names that exist in the Style Sheets that you added.
|
||||
|
||||
## External Style Sheet Location Kinds
|
||||
## External Style Sheet Location Kinds
|
||||
|
||||
There are three ways in which an external style sheet can be located:
|
||||
|
||||
* __Absolute Path/URL__ such as *C:\Application1\StyleSheets\StyleSheet1.xml* or *http://www.mysite.com/Application1/StyleSheets/StyleSheet1.xml*
|
||||
* __Absolute Path/URL__ such as *C:\Application1\StyleSheets\StyleSheet1.xml* or *https://www.mysite.com/Application1/StyleSheets/StyleSheet1.xml*
|
||||
* __Relative Path/URL__ such as *.\StyleSheets\StyleSheet1.xml* or *~/StyleSheets/StyleSheet1.xml*
|
||||
* __Resource Name__ such as *Application1.Resources.StyleSheet1.xml*
|
||||
|
||||
When you add a new external style sheet to the collection it will be recorded via Relative or Absolute path depending on the file's location. If the file that you chose is located __inside__ the current project root directory the style sheet will be recorded via relative path, otherwise it will be recorded via absolute path. Later you can change the way it is serialized by changing its location kind from the combo box next to its name.
|
||||
When you add a new external style sheet to the collection it will be recorded via Relative or Absolute path depending on the file's location. If the file that you chose is located __inside__ the current project root directory the style sheet will be recorded via relative path, otherwise it will be recorded via absolute path. Later you can change the way it is serialized by changing its location kind from the combo box next to its name.
|
||||
|
||||
## Absolute Path/URL
|
||||
## Absolute Path/URL
|
||||
|
||||
The external style sheet file does not have to be a part of the project since it is referenced absolutely.
|
||||
|
||||
|
|
@ -58,12 +58,12 @@ When deploying the style sheet file should be added to the project and should ha
|
|||
|
||||
## Relative Path/URL for type report definitions
|
||||
|
||||
When an external style sheet is referenced relatively the path is relative to the __hosting application root folder__. The project item representing the style sheet file should have its __"Copy to Output Directory"="Copy Always"__. When you use the Collection Editor, a project item for the style sheet file will be created automatically, if it does not exists, and it will be moved to a folder named __"StyleSheets"__ under the project root and its "Copy to Output Directory" property will be adjusted automatically as well.
|
||||
When an external style sheet is referenced relatively the path is relative to the __hosting application root folder__. The project item representing the style sheet file should have its __"Copy to Output Directory"="Copy Always"__. When you use the Collection Editor, a project item for the style sheet file will be created automatically, if it does not exists, and it will be moved to a folder named __"StyleSheets"__ under the project root and its "Copy to Output Directory" property will be adjusted automatically as well.
|
||||
|
||||
>note For Windows Forms projects, the root folder is the location of the executable file (by default bin folder). In Web applications the root folder is the root of the application. In this case the stylesheets should be copied to the root of the Web application as well.
|
||||
|
||||
## Resource Name
|
||||
|
||||
You can reference an external style sheet as an embedded resource by its __name__. The name should be the [case-sensitive name of the manifest resource being requested](http://msdn.microsoft.com/en-us/library/xc4235zt(VS.80).aspx). The project item representing the style sheet file should have its __"Build Action"="Embedded Resource"__. When you use the Collection Editor, a project item for the style sheet file will be created automatically, if it does not exists, it will be moved to a folder named __"Resources"__ under the project root and its "Build Action" property will be adjusted automatically as well. In the end the generated name will look something like *MyApplication1.Resources.StyleSheet1.xml* , where MyApplication1 is the default project namespace and the file is located in the folder Resources.
|
||||
You can reference an external style sheet as an embedded resource by its __name__. The name should be the [case-sensitive name of the manifest resource being requested](https://learn.microsoft.com/en-us/dotnet/api/system.reflection.assembly.getmanifestresourcestream?view=net-7.0#system-reflection-assembly-getmanifestresourcestream(system-string)). The project item representing the style sheet file should have its __"Build Action"="Embedded Resource"__. When you use the Collection Editor, a project item for the style sheet file will be created automatically, if it does not exists, it will be moved to a folder named __"Resources"__ under the project root and its "Build Action" property will be adjusted automatically as well. In the end the generated name will look something like *MyApplication1.Resources.StyleSheet1.xml* , where MyApplication1 is the default project namespace and the file is located in the folder Resources.
|
||||
|
||||
>note Specifying an URL for the external style sheet can be done only programmatically. It is not supported directly from the Collection Editor.
|
||||
|
|
|
|||
|
|
@ -15,11 +15,9 @@ This article explains the manual changes required when upgrading to Telerik Repo
|
|||
|
||||
## Map item changes
|
||||
|
||||
* The [ITileProvider](/reporting/api/Telerik.Reporting.ITileProvider) properties __TileImageFormat__ and __ImagerySet__ are no longer supported. When using [BingMapsTileProvider](/reporting/api/Telerik.Reporting.BingMapsTileProvider), you can set its [ImagerySet](/reporting/api/Telerik.Reporting.BingMapsTileProvider#Telerik_Reporting_BingMapsTileProvider_ImagerySet) property directly. For any other tile provider please use the [GenericTileProvider](/reporting/api/Telerik.Reporting.GenericTileProvider)'s [UrlTemplate](/reporting/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlTemplate) property.
|
||||
|
||||
* The [MapQuestTileProvider](/reporting/api/Telerik.Reporting.MapQuestTileProvider) is now obsolete and it is being substituted by the [GenericTileProvider](/reporting/api/Telerik.Reporting.GenericTileProvider). For backwards compatibility the reports designed using [MapQuestTileProvider](/reporting/api/Telerik.Reporting.MapQuestTileProvider) will still run, but a warning will be generated during compilation. To avoid this warning, consider using the [GenericTileProvider](/reporting/api/Telerik.Reporting.GenericTileProvider) class, which by default uses the [MapQuest](http://www.mapquest.com/) tile server settings. For more information see [Tile Providers]({%slug telerikreporting/designing-reports/report-structure/map/structure/tile-providers%}) documentation article.
|
||||
|
||||
* The [TileImageFormat](/reporting/api/Telerik.Reporting.TileProvider#Telerik_Reporting_TileProvider_TileImageFormat) property is now obsolete. When using [BingMapsTileProvider](/reporting/api/Telerik.Reporting.BingMapsTileProvider), the tiles image format will be automatically set by its [Imagery Metadata](http://msdn.microsoft.com/en-us/library/ff701712.aspx). For any other case you should be able to define it using the [UrlTemplate](/reporting/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlTemplate) property. For more information see [Tile Providers]({%slug telerikreporting/designing-reports/report-structure/map/structure/tile-providers%}) documentation article.
|
||||
* The [ITileProvider](/api/Telerik.Reporting.ITileProvider) properties `TileImageFormat` and `ImagerySet` are no longer supported. When using [BingMapsTileProvider](/api/Telerik.Reporting.BingMapsTileProvider), you can set its [ImagerySet](/api/Telerik.Reporting.BingMapsTileProvider#Telerik_Reporting_BingMapsTileProvider_ImagerySet) property directly. For any other tile provider please use the [GenericTileProvider](/api/Telerik.Reporting.GenericTileProvider)'s [UrlTemplate](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlTemplate) property.
|
||||
* The [MapQuestTileProvider](/api/Telerik.Reporting.MapQuestTileProvider) is now obsolete and it is being substituted by the [GenericTileProvider](/api/Telerik.Reporting.GenericTileProvider). For backwards compatibility the reports designed using [MapQuestTileProvider](/api/Telerik.Reporting.MapQuestTileProvider) will still run, but a warning will be generated during compilation. To avoid this warning, consider using the [GenericTileProvider](/api/Telerik.Reporting.GenericTileProvider) class, which by default uses the [MapQuest](https://www.mapquest.com/) tile server settings. For more information see [Tile Providers]({%slug telerikreporting/designing-reports/report-structure/map/structure/tile-providers%}) documentation article.
|
||||
* The [TileImageFormat](/api/Telerik.Reporting.TileProvider#Telerik_Reporting_TileProvider_TileImageFormat) property is now obsolete. When using [BingMapsTileProvider](/api/Telerik.Reporting.BingMapsTileProvider), the tiles image format will be automatically set by its [Imagery Metadata](https://learn.microsoft.com/en-us/bingmaps/rest-services/imagery/imagery-metadata). For any other case you should be able to define it using the [UrlTemplate](/api/Telerik.Reporting.GenericTileProvider#Telerik_Reporting_GenericTileProvider_UrlTemplate) property. For more information see [Tile Providers]({%slug telerikreporting/designing-reports/report-structure/map/structure/tile-providers%}) documentation article.
|
||||
|
||||
## WPF Report Viewer Dependencies
|
||||
|
||||
|
|
@ -27,11 +25,11 @@ The viewer is build with Telerik UI Controls for WPF 2014.1.331.40. If you are u
|
|||
|
||||
## Silverlight Report Viewer Dependencies
|
||||
|
||||
The viewer is build with Telerik UI Controls for Silverlight 2014.1.331.1050.
|
||||
The viewer is build with Telerik UI Controls for Silverlight 2014.1.331.1050.
|
||||
|
||||
## Standalone Report Designer
|
||||
|
||||
TRDX files created by the Standalone Report Designer contain XML version __http://schemas.telerik.com/reporting/2012/3.5__.
|
||||
TRDX files created by the Standalone Report Designer contain XML version `http://schemas.telerik.com/reporting/2012/3.5`.
|
||||
|
||||
## See Also
|
||||
|
||||
|
|
|
|||
|
|
@ -17,56 +17,52 @@ This article explains the manual changes required when upgrading to Telerik Repo
|
|||
|
||||
### WPF Report Viewer Dependencies
|
||||
|
||||
The viewer is build with Telerik UI Controls for WPF __2015.2.728.40__. If you are using a newer version consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}).
|
||||
The viewer is build with Telerik UI Controls for WPF `2015.2.728.40`. If you are using a newer version consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}).
|
||||
|
||||
### Silverlight Report Viewer Dependencies
|
||||
|
||||
The viewer is build with Telerik UI Controls for Silverlight __2015.2.728.1050__.
|
||||
The viewer is build with Telerik UI Controls for Silverlight `2015.2.728.1050`.
|
||||
|
||||
## Dependencies
|
||||
|
||||
### REST Report Service caching behavior
|
||||
|
||||
On report document retrieval the report service will not retrieve cached report by default. This can be managed with the request body as elaborated in [Resolve Document]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/documents-api/resolve-document%}) article.
|
||||
On report document retrieval the report service will not retrieve cached report by default. This can be managed with the request body as elaborated in [Resolve Document]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/documents-api/resolve-document%}) article.
|
||||
|
||||
### HTML5 Report Viewer and wrappers
|
||||
|
||||
Due to the changes in the REST Report Service you have to mandatory update the ReportViewer JavaScript (ReportViewer/js/telerikReportViewer-9.1.15.731.js).
|
||||
Due to the changes in the REST Report Service you have to mandatory update the ReportViewer JavaScript (ReportViewer/js/telerikReportViewer-9.1.15.731.js).
|
||||
|
||||
### HtmlTextBox
|
||||
|
||||
The HtmlTextBox now will decode any HTML content part of embedded expressions.
|
||||
The HtmlTextBox now will decode any HTML content part of embedded expressions.
|
||||
|
||||
### HTML5 Report Viewer Dependencies
|
||||
|
||||
The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) depends on the following libraries:
|
||||
The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) depends on the following libraries:
|
||||
|
||||
* Telerik Kendo UI (__2013.2.918__ or later)
|
||||
|
||||
* jQuery (__1.9.1__ or later)
|
||||
* Telerik Kendo UI (`2013.2.918` or later)
|
||||
* jQuery (`1.9.1` or later)
|
||||
|
||||
### HTML5 ASP.NET Web Forms Report Viewer Dependencies
|
||||
|
||||
The [HTML5 ASP.NET Web Forms Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-asp.net-web-forms-report-viewer/overview%}) depends on the following libraries:
|
||||
The [HTML5 ASP.NET Web Forms Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-asp.net-web-forms-report-viewer/overview%}) depends on the following libraries:
|
||||
|
||||
* The control is built on and requires [ASP.NET 4 Web Forms](http://www.asp.net/web-forms) or newer framework.
|
||||
|
||||
* Telerik Kendo UI (__2013.2.918__ or later)
|
||||
|
||||
* jQuery (__1.9.1__ or later)
|
||||
* The control is built on and requires [ASP.NET 4 Web Forms](https://learn.microsoft.com/en-us/aspnet/web-forms/) or newer framework.
|
||||
* Telerik Kendo UI (`2013.2.918` or later)
|
||||
* jQuery (`1.9.1` or later)
|
||||
|
||||
### ASP.NET WebAPI REST Report Service Dependencies
|
||||
|
||||
The [ASP.NET WebAPI REST Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/overview%}) requires the following assemblies:
|
||||
The [ASP.NET WebAPI REST Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/overview%}) requires the following assemblies:
|
||||
|
||||
* Microsoft ASP.NET Web API (__4.0.20710.0__ or later)
|
||||
|
||||
* Newtonsoft.Json (__4.5.11.15520__ or later)
|
||||
* Microsoft ASP.NET Web API (`4.0.20710.0` or later)
|
||||
* Newtonsoft.Json (`4.5.11.15520` or later)
|
||||
|
||||
### CubeDataSource Dependencies
|
||||
|
||||
If you are using [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}), the version of your Microsoft.AnalysisServices.AdomdClient should be __10.0.0.0__ or later.
|
||||
If you are using [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}), the version of your Microsoft.AnalysisServices.AdomdClient should be `10.0.0.0` or later.
|
||||
|
||||
### Standalone Report Designer
|
||||
|
||||
TRDX files created by the Standalone Report Designer contain XML version __http://schemas.telerik.com/reporting/2012/3.8__.
|
||||
TRDX files created by the Standalone Report Designer contain XML version `http://schemas.telerik.com/reporting/2012/3.8`.
|
||||
|
|
|
|||
|
|
@ -15,66 +15,58 @@ This article explains the manual changes required when upgrading to Telerik Repo
|
|||
|
||||
## Standalone Report Designer
|
||||
|
||||
TRDX files created by the Standalone Report Designer contain XML version __http://schemas.telerik.com/reporting/2012/3.8__.
|
||||
TRDX files created by the Standalone Report Designer contain XML version `http://schemas.telerik.com/reporting/2012/3.8`.
|
||||
|
||||
## Label Connectors for Bar Series
|
||||
|
||||
If your chart uses [BarSeries](/reporting/api/Telerik.Reporting.BarSeries), note that the newly introduced label connectors are visible by default. The above is applicable for both Cartesian and Polar coordinate systems.
|
||||
If your chart uses [BarSeries](/api/Telerik.Reporting.BarSeries), note that the newly introduced label connectors are visible by default. The above is applicable for both Cartesian and Polar coordinate systems.
|
||||
|
||||
## ASP.NET WebAPI REST Report Service implementation changes
|
||||
|
||||
* The [CreateReportResolver](/reporting/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_CreateReportResolver) method is now obsolete. Please use [ReportServiceConfiguration](/reporting/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) property instead.
|
||||
|
||||
* The [CreateCache](/reporting/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_CreateCache) method is now obsolete. Please use [ReportServiceConfiguration](/reporting/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) property instead.
|
||||
|
||||
* The [CreateStorage](/reporting/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_CreateStorage) method is now obsolete. Please use [ReportServiceConfiguration](/reporting/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) property instead.
|
||||
* The [CreateReportResolver](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_CreateReportResolver) method is now obsolete. Please use [ReportServiceConfiguration](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) property instead.
|
||||
* The [CreateCache](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_CreateCache) method is now obsolete. Please use [ReportServiceConfiguration](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) property instead.
|
||||
* The [CreateStorage](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_CreateStorage) method is now obsolete. Please use [ReportServiceConfiguration](/api/Telerik.Reporting.Services.WebApi.ReportsControllerBase#Telerik_Reporting_Services_WebApi_ReportsControllerBase_ReportServiceConfiguration) property instead.
|
||||
|
||||
## ServiceStack REST Report Service implementation changes
|
||||
|
||||
* The [CreateReportResolver](/reporting/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_CreateReportResolver) method is now obsolete. Please use [ReportServiceConfiguration](/reporting/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_ReportServiceConfiguration) property instead.
|
||||
|
||||
* The [CreateCache](/reporting/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_CreateCache) method is now obsolete. Please use [ReportServiceConfiguration](/reporting/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_ReportServiceConfiguration) property instead.
|
||||
|
||||
* The [CreateStorage](/reporting/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_CreateStorage) method is now obsolete. Please use [ReportServiceConfiguration](/reporting/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_ReportServiceConfiguration) property instead.
|
||||
* The [CreateReportResolver](/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_CreateReportResolver) method is now obsolete. Please use [ReportServiceConfiguration](/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_ReportServiceConfiguration) property instead.
|
||||
* The [CreateCache](/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_CreateCache) method is now obsolete. Please use [ReportServiceConfiguration](/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_ReportServiceConfiguration) property instead.
|
||||
* The [CreateStorage](/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_CreateStorage) method is now obsolete. Please use [ReportServiceConfiguration](/api/Telerik.Reporting.Services.ServiceStack.ReportsHostBase#Telerik_Reporting_Services_ServiceStack_ReportsHostBase_ReportServiceConfiguration) property instead.
|
||||
|
||||
## Changes
|
||||
|
||||
### WPF Report Viewer Dependencies
|
||||
|
||||
The viewer is build with Telerik UI Controls for WPF __2015.2.623.40__. If you are using a newer version consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}).
|
||||
The viewer is build with Telerik UI Controls for WPF `2015.2.623.40`. If you are using a newer version consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}).
|
||||
|
||||
### Silverlight Report Viewer Dependencies
|
||||
|
||||
The viewer is build with Telerik UI Controls for Silverlight __2015.2.623.1050__.
|
||||
The viewer is build with Telerik UI Controls for Silverlight `2015.2.623.1050`.
|
||||
|
||||
## Dependencies
|
||||
|
||||
### CubeDataSource Dependencies
|
||||
|
||||
If you are using [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}), the version of your Microsoft.AnalysisServices.AdomdClient should be __10.0.0.0__ or later.
|
||||
If you are using [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}), the version of your Microsoft.AnalysisServices.AdomdClient should be `10.0.0.0` or later.
|
||||
|
||||
### HTML5 Report Viewer Dependencies
|
||||
|
||||
The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) depends on the following libraries:
|
||||
The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) depends on the following libraries:
|
||||
|
||||
* Telerik Kendo UI (__2013.2.918__ or later)
|
||||
|
||||
* jQuery (__1.9.1__ or later)
|
||||
* Telerik Kendo UI (`2013.2.918` or later)
|
||||
* jQuery (`1.9.1` or later)
|
||||
|
||||
### HTML5 ASP.NET Web Forms Report Viewer Dependencies
|
||||
|
||||
The [HTML5 ASP.NET Web Forms Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-asp.net-web-forms-report-viewer/overview%}) depends on the following libraries:
|
||||
The [HTML5 ASP.NET Web Forms Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-asp.net-web-forms-report-viewer/overview%}) depends on the following libraries:
|
||||
|
||||
* The control is built on and requires [ASP.NET 4 Web Forms](http://www.asp.net/web-forms) or newer framework.
|
||||
|
||||
* Telerik Kendo UI (__2013.2.918__ or later)
|
||||
|
||||
* jQuery (__1.9.1__ or later)
|
||||
* The control is built on and requires [ASP.NET 4 Web Forms](https://learn.microsoft.com/en-us/aspnet/web-forms/) or newer framework.
|
||||
* Telerik Kendo UI (`2013.2.918` or later)
|
||||
* jQuery (`1.9.1` or later)
|
||||
|
||||
### ASP.NET WebAPI REST Report Service Dependencies
|
||||
|
||||
The [ASP.NET WebAPI REST Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/overview%}) requires the following assemblies:
|
||||
The [ASP.NET WebAPI REST Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/overview%}) requires the following assemblies:
|
||||
|
||||
* Microsoft ASP.NET Web API (__4.0.20710.0__ or later)
|
||||
|
||||
* Newtonsoft.Json (__4.5.11.15520__ or later)
|
||||
* Microsoft ASP.NET Web API (`4.0.20710.0` or later)
|
||||
* Newtonsoft.Json (`4.5.11.15520` or later)
|
||||
|
|
|
|||
|
|
@ -17,43 +17,40 @@ This article explains the manual changes required when upgrading to Telerik Repo
|
|||
|
||||
### Report Processing
|
||||
|
||||
DateTime scale shows axis label correctly when only one data point is displayed, instead of displaying January 1st of the current year.
|
||||
DateTime scale shows axis label correctly when only one data point is displayed, instead of displaying January 1st of the current year.
|
||||
|
||||
### Image Rendering
|
||||
|
||||
The Shape item rendering has changed. The Shape outlines are drawn with [Pen](https://msdn.microsoft.com/en-us/library/system.drawing.pen(v=vs.110).aspx) that has [Alignment](https://msdn.microsoft.com/en-us/library/system.drawing.pen.alignment(v=vs.110).aspx) set to [Inset](https://msdn.microsoft.com/en-us/library/z62ath7a(v=vs.110).aspx) in order to draw correctly closed figures.
|
||||
The Shape item rendering has changed. The Shape outlines are drawn with [Pen](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.pen?view=dotnet-plat-ext-7.0) that has [Alignment](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.pen.alignment?view=dotnet-plat-ext-7.0) set to [Inset](https://learn.microsoft.com/en-us/dotnet/api/system.drawing.drawing2d.penalignment?view=dotnet-plat-ext-7.0) in order to draw correctly closed figures.
|
||||
|
||||
### WPF Report Viewer
|
||||
|
||||
The viewer is build with Telerik UI Controls for WPF __2018.1.220.40__. If you are using a newer version consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}).
|
||||
The viewer is build with Telerik UI Controls for WPF `2018.1.220.40`. If you are using a newer version consider adding binding redirects. For more information see: [How to Add report viewer to a WPF .NET Framework project]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add-report-viewer-to-a-wpf-.net-framework-project%}).
|
||||
|
||||
### Silverlight Report Viewer
|
||||
|
||||
The viewer is build with Telerik UI Controls for Silverlight __2018.1.220.1050__.
|
||||
The viewer is build with Telerik UI Controls for Silverlight `2018.1.220.1050`.
|
||||
|
||||
## Dependencies
|
||||
|
||||
### Standalone Report Designer
|
||||
|
||||
TRDX, TRDP and TRBP files created by the Standalone Report Designer use schema version __http://schemas.telerik.com/reporting/2017/3.0__.
|
||||
TRDX, TRDP and TRBP files created by the Standalone Report Designer use schema version `http://schemas.telerik.com/reporting/2017/3.0`.
|
||||
|
||||
### HTML5 Report Viewer Dependencies
|
||||
|
||||
The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) depends on the following libraries:
|
||||
The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}) depends on the following libraries:
|
||||
|
||||
* Telerik Kendo UI (__2015.3.930__ or later)
|
||||
|
||||
* jQuery (__1.9.1__ or later)
|
||||
|
||||
* Browser's native support for promises. When the browser does not support promises the viewer will automatically load a promise polyfill from [Polyfill.io](https://polyfill.io) unless one is not already loaded in the application.
|
||||
* Telerik Kendo UI (`2015.3.930` or later)
|
||||
* jQuery (`1.9.1` or later)
|
||||
* Browser's native support for promises. When the browser does not support promises the viewer will automatically load a promise polyfill from [Polyfill.io](https://polyfill.io) unless one is not already loaded in the application.
|
||||
|
||||
### Angular Report Viewer Dependencies
|
||||
|
||||
The [Angular Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/angular-report-viewer-overview%}) depends on the following:
|
||||
The [Angular Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/angular-report-viewer/angular-report-viewer-overview%}) depends on the following:
|
||||
|
||||
* Angular (__4.0.0__ or later)
|
||||
|
||||
* jQuery (__3.2.1__)
|
||||
* Angular (`4.0.0` or later)
|
||||
* jQuery (`3.2.1`)
|
||||
|
||||
### WPF Report Viewer
|
||||
|
||||
|
|
@ -65,20 +62,19 @@ If you connect to a REST service or Report Server instance, you have to install
|
|||
|
||||
### ASP.NET WebAPI REST Report Service Dependencies
|
||||
|
||||
The [ASP.NET WebAPI REST Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/overview%}) requires the following assemblies:
|
||||
The [ASP.NET WebAPI REST Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/rest-api-reference/overview%}) requires the following assemblies:
|
||||
|
||||
* Microsoft ASP.NET Web API (__4.0.20710.0__ or later)
|
||||
|
||||
* Newtonsoft.Json (__4.5.11.15520__ or later)
|
||||
* Microsoft ASP.NET Web API (`4.0.20710.0` or later)
|
||||
* Newtonsoft.Json (`4.5.11.15520` or later)
|
||||
|
||||
### ServiceStack Report Service Dependencies
|
||||
|
||||
The [ServiceStack Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/servicestack-implementation/how-to-add-telerik-reporting-rest-servicestack-to-web-application%}) uses ServiceStack (__3.9.70.0__):
|
||||
The [ServiceStack Report Service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/servicestack-implementation/how-to-add-telerik-reporting-rest-servicestack-to-web-application%}) uses ServiceStack (`3.9.70.0`):
|
||||
|
||||
### CubeDataSource Dependencies
|
||||
|
||||
If you are using [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}), the version of your Microsoft.AnalysisServices.AdomdClient should be __10.0.0.0__ or later.
|
||||
If you are using [CubeDataSource]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/cubedatasource-component/overview%}), the version of your Microsoft.AnalysisServices.AdomdClient should be `10.0.0.0` or later.
|
||||
|
||||
### Database Cache Provider Dependencies
|
||||
|
||||
If you are using [Database Cache Provider]({%slug telerikreporting/using-reports-in-applications/export-and-configure/cache-management/other-reportviewer-controls/configuring-the-database-cache-provider%}), the version of your Telerik Data Access ORM should be __2015.1.225.1__ or later.
|
||||
If you are using [Database Cache Provider]({%slug telerikreporting/using-reports-in-applications/export-and-configure/cache-management/other-reportviewer-controls/configuring-the-database-cache-provider%}), the version of your Telerik Data Access ORM should be `2015.1.225.1` or later.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Overview
|
||||
page_title: Upgrade Overview
|
||||
page_title: Upgrade Overview
|
||||
description: "Learn more about the general flow when upgrading Telerik Reporting and using the major and minor releases, and upgrade desktop, website, and other projects manually."
|
||||
slug: telerikreporting/upgrade/overview
|
||||
tags: telerik, reporting, upgrading, major, minor, releases, desktop, website, other, projects, manually, overview
|
||||
|
|
@ -17,106 +17,81 @@ Depending on the new features and changes in each new Telerik Reporting release,
|
|||
|
||||
To upgrade Telerik Reporting:
|
||||
|
||||
1. Check for any new features, fixes, breaking or dependency changes in the Telerik Reporting [Release History](https://www.telerik.com/support/whats-new/reporting/release-history).
|
||||
|
||||
1. Install the desired Telerik Reporting version by using the Telerik Control Panel or [through the MSI installer file]({%slug telerikreporting/installation%}).
|
||||
|
||||
1. Upgrade all projects that use Telerik Reporting as described in this article.
|
||||
|
||||
1. Check for any updates between your current and desired versions in the articles with the specific changes in each Telerik Reporting release. For example, if your project currently targets Q3 2013, to upgrade to Q1 2014, review the articles for [Q3 2013]({% slug telerikreporting/upgrade/2013/q3-2013 %}) and [Q1 2014]({% slug telerikreporting/upgrade/2014/q1-2014 %}).
|
||||
1. Check for any new features, fixes, breaking or dependency changes in the Telerik Reporting [Release History](https://www.telerik.com/support/whats-new/reporting/release-history).
|
||||
1. Install the desired Telerik Reporting version by using the Telerik Control Panel or [through the MSI installer file]({%slug telerikreporting/installation%}).
|
||||
1. Upgrade all projects that use Telerik Reporting as described in this article.
|
||||
1. Check for any updates between your current and desired versions in the articles with the specific changes in each Telerik Reporting release. For example, if your project currently targets Q3 2013, to upgrade to Q1 2014, review the articles for [Q3 2013]({%slug telerikreporting/upgrade/2013/q3-2013%}) and [Q1 2014]({%slug telerikreporting/upgrade/2014/q1-2014%}).
|
||||
|
||||
For any persisting issues, use either of the following options:
|
||||
|
||||
* Refer to the article on [troubleshooting installation and upgrade issues]({%slug unable-to-upgrade-after-wizard %}) in Telerik Reporting.
|
||||
|
||||
* Send the issue through the [dedicated Telerik Reporting support system](https://www.telerik.com/support/reporting) together with your project or solution in a `.zip` file.
|
||||
* Refer to the article on [troubleshooting installation and upgrade issues]({%slug unable-to-upgrade-after-wizard%}) in Telerik Reporting.
|
||||
* Send the issue through the [dedicated Telerik Reporting support system](https://www.telerik.com/support/reporting) together with your project or solution in a `.zip` file.
|
||||
|
||||
## Major and Minor Releases
|
||||
|
||||
Telerik Reporting supports the following types of releases:
|
||||
Telerik Reporting supports the following types of releases:
|
||||
|
||||
* Major versions—They can simultaneously coexist on the same machine. For example, major versions are the [Q3 2013]({% slug telerikreporting/upgrade/2013/q3-2013 %}) and [Q1 2014]({% slug telerikreporting/upgrade/2014/q1-2014 %}) releases.
|
||||
* Major versions—They can simultaneously coexist on the same machine. For example, major versions are the [Q3 2013]({%slug telerikreporting/upgrade/2013/q3-2013%}) and [Q1 2014]({%slug telerikreporting/upgrade/2014/q1-2014%}) releases.
|
||||
* Minor versions, or Service Packs (SP)—A major version can coexist on the same machine with only a single minor version from the same release. For example, when you upgrade the major Q1 2014 release to the later minor Q1 2014 SP1 release, the installer will first uninstall the Q1 2014 version and then install Q1 2014 SP1.
|
||||
|
||||
* Minor versions, or Service Packs (SP)—A major version can coexist on the same machine with only a single minor version from the same release. For example, when you upgrade the major Q1 2014 release to the later minor Q1 2014 SP1 release, the installer will first uninstall the Q1 2014 version and then install Q1 2014 SP1.
|
||||
|
||||
If the new Telerik Reporting version is a major release, it will be installed next to the earlier releases. If the new Telerik Reporting version is a minor release, it will replace the corresponding major release.
|
||||
|
||||
> Visual Studio Toolbox loads only the updates from the latest Telerik Reporting version that is installed on your computer. However, you will be able to work with the item and project templates from all Telerik Reporting versions that are installed on your computer.
|
||||
If the new Telerik Reporting version is a major release, it will be installed next to the earlier releases. If the new Telerik Reporting version is a minor release, it will replace the corresponding major release.
|
||||
|
||||
> Visual Studio Toolbox loads only the updates from the latest Telerik Reporting version that is installed on your computer. However, you will be able to work with the item and project templates from all Telerik Reporting versions that are installed on your computer.
|
||||
|
||||
## Upgrading Projects Automatically
|
||||
|
||||
To automatically upgrade your project to a later Telerik Reporting version, use the [Telerik Upgrade Wizard]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/upgrade-wizard%}).
|
||||
To automatically upgrade your project to a later Telerik Reporting version, use the [Telerik Upgrade Wizard]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/upgrade-wizard%}).
|
||||
|
||||
The Telerik Upgrade Wizard does not support website projects because [websites handle the assembly references in a different way](https://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx). To upgrade your website project automatically, transform it into a web application. Alternatively, [upgrade your website project manually](#upgrading-website-projects-manually).
|
||||
The Telerik Upgrade Wizard does not support website projects because [websites handle the assembly references in a different way](https://learn.microsoft.com/en-us/previous-versions/aspnet/dd547590(v=vs.110)). To upgrade your website project automatically, transform it into a web application. Alternatively, [upgrade your website project manually](#upgrading-website-projects-manually).
|
||||
|
||||
The Telerik Upgrade Wizard does not support .NET Core projects. To upgrade your .NET project, manually upgrade the references to the Telerik Reporting assemblies or NuGet packages and the HTML5 Report Viewer scripts to the required version.
|
||||
The Telerik Upgrade Wizard does not support .NET Core projects. To upgrade your .NET project, manually upgrade the references to the Telerik Reporting assemblies or NuGet packages and the HTML5 Report Viewer scripts to the required version.
|
||||
|
||||
You can only manually update website, WPF, and Silverlight projects which use the WPF and Silverlight Report Viewers but do not have separately purchased Telerik UI for WPF and Telerik UI for Silverlight products.
|
||||
|
||||
## Upgrading Projects Manually
|
||||
|
||||
You can manually upgrade class library and website projects, and desktop and web applications.
|
||||
You can manually upgrade class library and website projects, and desktop and web applications.
|
||||
|
||||
1. In `Solution Explorer`, click the __Show All Files__ button. Open __References__ and locate the references to the previous Telerik Reporting assemblies.
|
||||
1. In `Solution Explorer`, click the __Show All Files__ button. Open __References__ and locate the references to the previous Telerik Reporting assemblies.
|
||||
|
||||
Service Pack assemblies are marked with yellow exclamation marks which show that the assemblies cannot be located. This behavior is normal and indicates that you have an uninstalled the version to which they belong.
|
||||
|
||||
1. Select the old assemblies that you identified in the previous step and click __Delete__ to remove them. Keep the names of the deleted assemblies for further reference.
|
||||
|
||||
1. Right-click __References__ and select __Add Reference__ > __Add all__ to add all required references to the new Telerik Reporting assembly versions. These versions correspond to the deleted ones from the previous step. As a result, the newly added references appear in __References__ without the yellow exclamation marks which means that they are valid.
|
||||
Service Pack assemblies are marked with yellow exclamation marks which show that the assemblies cannot be located. This behavior is normal and indicates that you have an uninstalled the version to which they belong.
|
||||
|
||||
1. Select the old assemblies that you identified in the previous step and click __Delete__ to remove them. Keep the names of the deleted assemblies for further reference.
|
||||
1. Right-click __References__ and select __Add Reference__ > __Add all__ to add all required references to the new Telerik Reporting assembly versions. These versions correspond to the deleted ones from the previous step. As a result, the newly added references appear in __References__ without the yellow exclamation marks which means that they are valid.
|
||||
1. Open the `web.config/app.config` file and update all version numbers to the new one in the following instances:
|
||||
|
||||
+ `<configSections>`―The location in which you can alter the attributes of the rendering extensions.
|
||||
+ `<configSections>`―The location in which you can alter the attributes of the rendering extensions.
|
||||
+ `<httpHandlers>`/`<handlers>`―The location in which the ASP.NET Report Viewer registers its handler.
|
||||
+ `<assemblies>`―The Reporting assemblies that are references in the web application.
|
||||
|
||||
+ `<httpHandlers>`/`<handlers>`―The location in which the ASP.NET Report Viewer registers its handler.
|
||||
1. (For web applications only) Open the `.aspx` or `.master` pages and change the version of the ASP.NET Report Viewer in the `Register` directive. Update the HTML5 Report Viewer files in the project. Open the `.cshtml` or `.vbhtml` and layout views, the pure HTML pages or the `.aspx` or `.master` pages, and change the version of the links which point to the following files:
|
||||
|
||||
+ `<assemblies>`―The Reporting assemblies that are references in the web application.
|
||||
+ `telerikReportViewer-x.x.x.x(.min).css`―The CSS of the HTML5 Report Viewer where `x.x.x.x` is the HTML5 Report Viewer and Telerik Reporting version (for example, `8.1.14.816`).
|
||||
+ `telerikReportViewer-x.x.x.x(.min).js`―The JavaScript files of the HTML5 Report Viewer where `x.x.x.x` is the HTML5 Report Viewer and Telerik Reporting version (for example, `8.1.14.816`).
|
||||
+ `telerikReportViewerTemplate.html`―The default HTML template page of the HTML5 Report Viewer.
|
||||
|
||||
1. (For web applications only) Open the `.aspx` or `.master` pages and change the version of the ASP.NET Report Viewer in the `Register` directive. Update the HTML5 Report Viewer files in the project. Open the `.cshtml` or `.vbhtml` and layout views, the pure HTML pages or the `.aspx` or `.master` pages, and change the version of the links which point to the following files:
|
||||
(For WPF applications only) Update the references to Telerik UI for WPF and the corresponding binding redirects, if any. For more information, refer to the article on [manually setting up the WPF ReportViewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add--manually-report-viewer-to-a-wpf-.net-framework-project%}). Update the XAML resources which correspond to the updated Telerik UI for WPF assemblies.
|
||||
|
||||
+ `telerikReportViewer-x.x.x.x(.min).css`―The CSS of the HTML5 Report Viewer where `x.x.x.x` is the HTML5 Report Viewer and Telerik Reporting version (for example, `8.1.14.816`).
|
||||
|
||||
+ `telerikReportViewer-x.x.x.x(.min).js`―The JavaScript files of the HTML5 Report Viewer where `x.x.x.x` is the HTML5 Report Viewer and Telerik Reporting version (for example, `8.1.14.816`).
|
||||
|
||||
+ `telerikReportViewerTemplate.html`―The default HTML template page of the HTML5 Report Viewer.
|
||||
|
||||
(For WPF applications only) Update the references to Telerik UI for WPF and the corresponding binding redirects, if any. For more information, refer to the article on [manually setting up the WPF ReportViewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/wpf-application/how-to-add--manually-report-viewer-to-a-wpf-.net-framework-project%}). Update the XAML resources which correspond to the updated Telerik UI for WPF assemblies.
|
||||
|
||||
(For Silverlight applications only) [Update the references to Telerik UI for Silverlight]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/silverlight-application/how-to-add-report-viewer-to-a-silverlight-application%}) and the XAML resources which correspond to the updated Telerik UI for Silverlight assemblies.
|
||||
|
||||
1. Open all report resource files as XML―each `.resx` file appears under the respective report file. Locate all occurrences of a Telerik Reporting Assembly and update the version number to the new one. Unlike the version name (for example, `Q1 2008`), the version number is a technical identifier (for example, `2.5.8.414`).
|
||||
|
||||
1. Restart Visual Studio and rebuild all updated projects.
|
||||
(For Silverlight applications only) [Update the references to Telerik UI for Silverlight]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/silverlight-application/how-to-add-report-viewer-to-a-silverlight-application%}) and the XAML resources which correspond to the updated Telerik UI for Silverlight assemblies.
|
||||
|
||||
1. Open all report resource files as XML―each `.resx` file appears under the respective report file. Locate all occurrences of a Telerik Reporting Assembly and update the version number to the new one. Unlike the version name (for example, `Q1 2008`), the version number is a technical identifier (for example, `2.5.8.414`).
|
||||
1. Restart Visual Studio and rebuild all updated projects.
|
||||
1. If compilation errors or warnings occur, review the Telerik Reporting [Release History](https://www.telerik.com/support/whats-new/reporting/release-history) for any obsolete or deleted properties, methods, and events, and handle these according to the instructions. Review the release history for all releases between the previous and the latest version you installed.
|
||||
|
||||
|
||||
## Upgrading Website Projects Manually
|
||||
|
||||
To upgrade your website project manually:
|
||||
To upgrade your website project manually:
|
||||
|
||||
1. In `Solution Explorer`, click the __Show All Files__ button. Select __Delete all__ to remove all Telerik Reporting assemblies from the `Bin` folder.
|
||||
|
||||
1. From the __References__ tab on the __Property Pages__ of the website, remove all references to Telerik Reporting assemblies. Keep the names of the deleted assemblies for further reference.
|
||||
|
||||
1. Select __Add all__ to add all required references to the new Telerik Reporting assembly versions. They correspond to the ones that you deleted in the previous step.
|
||||
|
||||
1. Open the `web.config` file and update all version numbers to the new one in the following instances:
|
||||
|
||||
+ `<configSections>`―The location in which you can alter the attributes of the rendering extensions.
|
||||
|
||||
+ `<httpHandlers>`/`<handlers>`―The location in which the ASP.NET Report Viewer registers its handler.
|
||||
|
||||
+ `<assemblies>`―The Telerik Reporting assemblies that are referenced in the website.
|
||||
|
||||
1. Open the `.aspx/.master` pages and change the version of the Report Viewer in the `Register` directive.
|
||||
|
||||
1. Open all report resource files as XML―Each `.resx` file appears under the respective report file. Locate all occurrences of a Telerik Reporting Assembly and update their version number to the new one. Unlike the version name (for example, Q1 2014), the version number is a technical identifier (for example, 8.0.14.225).
|
||||
|
||||
1. Restart Visual Studio and rebuild all updated projects.
|
||||
|
||||
1. If compilation errors or warnings occur, review the Telerik Reporting [Release History](https://www.telerik.com/support/whats-new/reporting/release-history) for any obsolete or deleted properties, methods, and events, and handle these according to the instructions. Review the Release History for all releases between the previous and the latest version you installed.
|
||||
1. In `Solution Explorer`, click the __Show All Files__ button. Select __Delete all__ to remove all Telerik Reporting assemblies from the `Bin` folder.
|
||||
1. From the __References__ tab on the __Property Pages__ of the website, remove all references to Telerik Reporting assemblies. Keep the names of the deleted assemblies for further reference.
|
||||
1. Select __Add all__ to add all required references to the new Telerik Reporting assembly versions. They correspond to the ones that you deleted in the previous step.
|
||||
1. Open the `web.config` file and update all version numbers to the new one in the following instances:
|
||||
|
||||
+ `<configSections>`―The location in which you can alter the attributes of the rendering extensions.
|
||||
+ `<httpHandlers>`/`<handlers>`―The location in which the ASP.NET Report Viewer registers its handler.
|
||||
+ `<assemblies>`―The Telerik Reporting assemblies that are referenced in the website.
|
||||
|
||||
1. Open the `.aspx/.master` pages and change the version of the Report Viewer in the `Register` directive.
|
||||
1. Open all report resource files as XML―Each `.resx` file appears under the respective report file. Locate all occurrences of a Telerik Reporting Assembly and update their version number to the new one. Unlike the version name (for example, Q1 2014), the version number is a technical identifier (for example, 8.0.14.225).
|
||||
1. Restart Visual Studio and rebuild all updated projects.
|
||||
1. If compilation errors or warnings occur, review the Telerik Reporting [Release History](https://www.telerik.com/support/whats-new/reporting/release-history) for any obsolete or deleted properties, methods, and events, and handle these according to the instructions. Review the Release History for all releases between the previous and the latest version you installed.
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче