You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore: StackExchange.Redis version bump
Updated the reference of StackExchange.Redis from 2.0.601 to 2.6.122.
* docs: updated versions, added known issue
- updated versions of NARV deps
- updated SRD-NET
- updated StackExchange.Redis version
- added known issue with SRD-NET on .NET 8 - styleRule and ReportParam.
* docs: added info for SRD.NET 8
- added info for .NET 8;
- updated the starting routine;
- added info for --roll-forward feature.
Refs: #1635
* docs: OpenXml 3.0.1 changes
Added info for new .dll we start distributing with 2024 Q1
* docs: GlobalObjects.Environment
Added info for Environment type in GlobalObjects functions.
* Update global-objects.md
* Update overview.md
* Update 2024-q1.md
* docs: upgrade path with WPF/WinUI versions
Set correct versions of WPF and WinUI assemblies
Removed the Known Issues section - it's now fixed.
Refs: no issue.
* Update _config.yml
---------
Co-authored-by: Todor Arabadzhiev <[email protected]>
Copy file name to clipboardExpand all lines: designing-reports/connecting-to-data/expressions/expressions-reference/global-objects.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,17 @@ Examples:
37
37
38
38
Another option for accessing the report parameters' collection is the global function [Parameters(parameterName)]({%slug telerikreporting/designing-reports/connecting-to-data/expressions/expressions-reference/functions/report-functions%}).
39
39
40
+
## Environment
41
+
42
+
Represents a read-only type that contains information about the environment in which the reporting engine works. Contains two properties: `OperatingSystem` and `GraphicsEngine`.
43
+
44
+
*`OperatingSystem` returns the identifier of the operating system in which the current application is running, as provided by the [OperatingSystem.VersionString](https://learn.microsoft.com/en-us/dotnet/api/system.operatingsystem.versionstring) property (e.g. 'Microsoft Windows NT 6.2.9200.0').
45
+
*`GraphicsEngine` returns a [GraphicsEngine](/api/telerik.drawing.contract.graphicsengine) member representing the currently used graphics engine. Available values: `Gdi` and `Skia`, accessible also through the **ReportingConstants.GraphicsEngine** options. Example: `=Switch(Environment.GraphicsEngine, GraphicsEngine.Gdi, "Using GDI", GraphicsEngine.Skia, "Using Skia", "N\A")`
46
+
47
+
## ExecutionTime
48
+
49
+
A [DateTime](https://learn.microsoft.com/en-us/dotnet/api/system.datetime) instance containing the date and time of the moment when the current report started its procesing by the reporting engine.
50
+
40
51
## PageNumber
41
52
42
53
The current page number. It can be used only in the page header and footer.
Copy file name to clipboardExpand all lines: designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md
+19-8Lines changed: 19 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,15 +20,16 @@ The Standalone Report Designer empowers report authors with creating, editing, a
20
20
The Standalone Report Designer is distributed as a single EXE file, which simplifies its distribution and does not require installation. Visual Studio is not required to create reports with the Standalone Report Designer. Reports are processed on the client's machine.
21
21
22
22
Since its introduction in 2013 R2, the Standalone Report Designer is built against .NET Framework 4.0 and is distributed as a part of the Telerik Reporting package. The designer comes in two flavors - Telerik.ReportDesigner.x86.exe which is compiled as a 32-bit application, and Telerik.ReportDesigner.exe, which is compiled as a 64-bit application.
23
-
Starting with 2022 R3, a new version of Standalone Report Designer is available. It is named Telerik.ReportDesigner.Net and is built against .NET 6.0. Its main purpose is to allow the report authors to load and use their assemblies compiled against .NET Standard, .NET Core, and .NET 5+. The Standalone Report Designer for .NET is currently distributed as two .ZIP packages, each for the corresponding x86 or x64 flavor of the application.
23
+
24
+
Starting with 2022 R3, a new version of Standalone Report Designer is available. It is named Telerik.ReportDesigner.Net and originally was built against .NET 6. With 2024 Q1 its target framework was changed to .NET 8. Its main purpose is to allow the report authors to load and use their assemblies compiled against .NET Standard, .NET Core, and .NET 5+. The Standalone Report Designer for .NET is distributed with the product installer, and also as .ZIP packages, containing the x86 or x64 flavor of the application.
24
25
25
26
## Differences between the .NET and .NET Framework designers' functionality
26
27
27
-
This section explains the differences between both versions of Standalone Report Designer - for .NET Framework and .NET 6.0. Although lots of code was shared between the versions, the .NET induced some changes that are listed below.
28
+
This section explains the differences between both versions of Standalone Report Designer - for .NET Framework and .NET 8. Although lots of code was shared between the versions, the .NET induced some changes that are listed below.
28
29
29
30
*__Automatic discovery of 3rd party ADO.NET Data Providers__ - The Standalone Report Designer for the .NET Framework required manually adding an entry in the DbProviderFactories section in the application configuration file when needed to use a third-party ADO.NET provider. The Report Designer for .NET will try to discover and automatically load the available ADO.NET data providers when building a new SQL connection. The supported providers are: `Microsoft.Data.SqlClient`, `System.Data.SqlClient`, `Npgsql for PostgreSQL`, `System.Data.SQLite`, `MySql.Data.MySqlClient`, `Oracle.ManagedDataAccess.Client`. `ODBC` and `OleDB` data sources are also supported.
30
31
31
-
> If any of the supported data providers doesn't appear in the dropbox of the SqlDataSource wizard you need to add its DLL in the folder with the `Telerik.ReportDesigner.Net.exe` file.
32
+
> If any of the supported data providers doesn't appear in the dropbox of the SqlDataSource wizard you need to add its .dll and its dependency .dll files in the folder with the `Telerik.ReportDesigner.Net.exe` file.
32
33
33
34
*__Query Builder__ - the Query Builder uses Telerik OpenAccess to define the relations between the tables in a database. Telerik OpenAccess has limited support for .NET, so currently the Query Builder functionality for the .NET designer is restricted.
34
35
*__Import Report Wizard__ - the Import Report functionality relies on external 3rd-party assemblies that do not have .NET-compatible versions. The Import Report Wizard option is not available on the .NET designer's initial page.
@@ -50,13 +51,23 @@ This section explains the differences between both versions of Standalone Report
50
51
51
52
*__From your Telerik Account:__
52
53
53
-
1. Navigate to the Progress Telerik Reporting installation folder. By default, it is `%PROGRAMFILES(x86)%\Progress\`.
54
-
1. Navigate to the `.net` subfolder.
54
+
1. Navigate to the Progress Telerik Reporting installation folder. By default, it is `%PROGRAMFILES(x86)%\Progress\Telerik Reporting YYYY RR` where YYYY RR stands for the currently installed year and release moniker.
55
+
1. Navigate to the `Report Designer\.NET` subfolder.
55
56
1. Start the Telerik.ReportDesigner.Net.exe to run the 64-bit flavor of Standalone Report Designer for .NET.
56
57
1. Navigate to the `x86` subfolder and start the Telerik.ReportDesigner.Net.x86.exe to run the 32-bit flavor of Standalone Report Designer for .NET.
57
58
1. The Standalone Report Designer opens, and you can create or open a report.
58
59
59
-
## Major UI Elements in the Standalone Report Designer
60
+
*__Starting Standalone Report Designer using the latest installed .NET runtime:__
61
+
The Standalone Report Designer will be targeting LTS (Long-Term-Support) versions of .NET. If it is necessary to run the application against STS (Standard-Term-Support) .NET versions like .NET 9, or a pre-release version of LTS .NET, please use the `RollForward` feature of .NET runtime. Start the Standalone Report Designer from a command prompt, adding the `--roll-forward` parameter:
For further information about controlling the `RollForward` behavior at runtime, check the related Microsoft documentation article section [Control roll-forward behavior](https://learn.microsoft.com/en-us/dotnet/core/versions/selection#control-roll-forward-behavior).
69
+
70
+
## Major UI Elements in the Standalone Report Designer
60
71
61
72
62
73
@@ -65,7 +76,7 @@ The image above shows the major UI elements in the Standalone Report Designer:
65
76
* __View tab:__ Lets you open the [Report Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/report-explorer%}), [Data Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/data-explorer%}), [Group Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/group-explorer%}), __Property Browser__ or navigate to __Startup Page__
66
77
* __Report selector button:__ Clicking this button makes the report active in the `Properties` window.
67
78
* __Rulers:__ Located on the top and left side of the designer, they provide a point of reference for the report layout.
68
-
*__Report Sections__: The high-level report design consists of report sections for the report header, report footer, page header, page footer, detail, group header, and group footer. Each section can be resized by dragging the sizing grips at the bottom/right of each section. Most sections except the detail can be deleted by selecting the section and hitting the delete key. To delete a group section, you have to delete the whole group from the [Group Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/group-explorer%})
79
+
* __Report Sections__: The high-level report design consists of report sections for the report header, report footer, page header, page footer, detail, group header, and group footer. Each section can be resized by dragging the sizing grips at the bottom/right of each section. Most sections except the detail can be deleted by selecting the section and hitting the delete key. To delete a group section, you have to delete the whole group from the [Group Explorer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/group-explorer%})
69
80
* __Component Tray:__ Shows the [DataSource components]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/overview%}) that are used in this report.
70
81
* __View Mode Buttons:__ Use these buttons to switch between the `Design`, and `Preview` views.
71
82
* [Context Menu]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/tools/context-menu%}) (not shown on the image above): Appears on right-click and conditionally displays content depending on the area that was right-clicked.
@@ -74,7 +85,7 @@ The image above shows the major UI elements in the Standalone Report Designer:
74
85
75
86
Additionally, the Standalone Report Designer includes the following helpful elements:
76
87
77
-
*__ToolStrip__: This is a UI element that includes various buttons that are designed to ease you while you design reports. The `ToolStrip`, which is shown in the image below, is placed in the lower-left corner of the design surface.
88
+
* __ToolStrip__: This is a UI element that includes various buttons that are designed to ease you while you design reports. The `ToolStrip`, which is shown in the image below, is placed in the lower-left corner of the design surface.
78
89
79
90
Copy file name to clipboardExpand all lines: getting-started/installation/third-party-dependencies.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,9 +28,10 @@ To export its reports in Open XML formats, such as `.docx`, `.xlsx`, or `.pptx`,
28
28
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:
29
29
30
30
*`Telerik.Reporting.OpenXmlRendering.dll`−Supports 2.0.5022.0 and 2.5.5631.0 `DocumentFormat.OpenXml.dll` versions.
31
-
*`Telerik.Reporting.OpenXmlRendering.2.7.2.dll`−Supports 2.7.2.0 and later `DocumentFormat.OpenXml.dll` versions.
31
+
*`Telerik.Reporting.OpenXmlRendering.2.7.2.dll`−Supports 2.7.2.0 and later `DocumentFormat.OpenXml.dll` versions up to version 3.x.x.x
32
+
*`Telerik.Reporting.OpenXmlRendering.3.0.1.dll`−Supports 3.0.1.0 and later `DocumentFormat.OpenXml.dll` versions.
32
33
33
-
>Currently, we do not support DocumentFormat.OpenXml `3.x.x` due to breaking changes. To generate compatible document types, always use the latest available `2.x.x` 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 .NET Framework applications.
34
+
>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 .NET Framework applications.
34
35
35
36
To download Open XML by using the NuGet feed, refer to the [`DocumentFormat.OpenXml` NuGet package](https://www.nuget.org/packages/DocumentFormat.OpenXml/).
Copy file name to clipboardExpand all lines: knowledge-base/deploy-telerik-reporting-with-newer-openxml-sdk-version.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ Still, if needed, you can use *newer* Open XML SDK version. Add a binding redire
42
42
...
43
43
````
44
44
45
-
In newer versions, the DocumentFormat.OpenXml assembly the **PublicKeyToken** is changed. Thus, if you are using DocumentFormat.OpenXml of version **2.7.2.0**, you have to reference **Telerik.Reporting.OpenXmlRendering.2.7.2.**
45
+
In newer versions, the DocumentFormat.OpenXml assembly the **PublicKeyToken** is changed. Thus, if you are using DocumentFormat.OpenXml of version **2.7.2.0** or later, you have to reference **Telerik.Reporting.OpenXmlRendering.2.7.2.**or **Telerik.Reporting.OpenXmlRendering.3.0.1.**
46
46
47
47
For even newer versions add the required binding redirect as shown in the following example configuration for DocumentFormat.OpenXml 2.8.1.0:
Copy file name to clipboardExpand all lines: knowledge-base/exporting-reports-excel-not-working-after-upgrade.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,4 +66,5 @@ CSharp.Net7.Html5IntegrationDemo Error: 0 : An error occurred while rendering th
66
66
67
67
# Solution
68
68
69
-
To resolve this issue, you need to ensure that the 'DocumentFormat.OpenXml' version referenced in the project is 2.7.2 or higher, but lower than 3.0.0.
69
+
- If you are using version of Telerik Reporting prior to 2024 Q1 (18.0.24.130), you need to ensure that the 'DocumentFormat.OpenXml' version referenced in the project is 2.7.2 or higher, but lower than 3.0.0.
70
+
- If you are using version of Telerik Reporting version 18.0.24.130 or newer, please reference 'Telerik.Reporting.OpenXmlRendering.3.0.1' which works with 'DocumentFormat.OpenXml' version 3.0.1 or newer.
Copy file name to clipboardExpand all lines: knowledge-base/missing-docx-xlsx-pptx-xps-export-options.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,9 @@ The `XPS` rendering extension requires the `Telerik.Reporting.XpsRendering.dll`
56
56
57
57
If you are using `DocumentFormat.OpenXml` of version `2.5.5631.0`, you will need binding redirect for the `DocumentFormat.OpenXml.dll` assembly - [Deploy Telerik Reporting with newer OpenXML SDK version]({%slug deploy-telerik-reporting-with-newer-openxml-sdk-version%}).
58
58
59
-
In newer versions of the `DocumentFormat.OpenXml` assembly the `PublicKeyToken` is changed. Thus, if you are using `DocumentFormat.OpenXml` of version `2.7.2.0` you have to reference `Telerik.Reporting.OpenXmlRendering.2.7.2.`
59
+
In newer versions of the `DocumentFormat.OpenXml` assembly the `PublicKeyToken` is changed. Thus, if you are using `DocumentFormat.OpenXml` of version `2.7.2.0` or newer you have to reference `Telerik.Reporting.OpenXmlRendering.2.7.2.` or `Telerik.Reporting.OpenXmlRendering.3.0.1.`
60
+
61
+
**Note:**`Telerik.Reporting.OpenXmlRendering.3.0.1.` is introduced in Telerik Reporting 2024 Q1 (18.0.24.130)
60
62
61
63
> For even newer versions, also add the required `binding redirect`.
0 commit comments