From 0be62c733a49951086e91f4e5ad54fad6b17897e Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Thu, 12 Jun 2025 16:37:21 +0300 Subject: [PATCH 1/6] docs: address dotnet 6 deprecation issues --- .../connecting-the-sqldatasource-component-to-a-data-source.md | 2 +- .../desktop-designers/standalone-report-designer/overview.md | 2 +- doc-output/configure-the-report-engine/processing-element.md | 2 +- embedding-reports/asp-net-core-reporting.md | 2 +- embedding-reports/blazor-reporting.md | 2 +- .../host-reports-service-in-.net-5.md | 2 +- .../host-reports-service-in-.net-6-with-minimal-api.md | 2 +- .../host-reports-service-in-.net-with-controllers.md | 2 +- embedding-reports/overview.md | 3 ++- embedding-reports/spa-reporting.md | 2 +- 10 files changed, 11 insertions(+), 10 deletions(-) diff --git a/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md b/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md index 48559bc56..69a339798 100644 --- a/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md +++ b/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md @@ -30,7 +30,7 @@ The following example shows how to connect to the __SQL Server AdventureWorks__ ```` -Configuration files in XML format are used in .NET Framework applications. In .NET Core and .NET 6+ applications, the configuration file usually is in JSON-format and is called `appsettings.json`. The configuration of connection strings section is explained in the following documentation article: [How to Host Reports Service in ASP.NET Core in .NET {{site.mindotnetversion}}]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-in-.net-6-with-minimal-api%}). +Configuration files in XML format are used in .NET Framework applications. In .NET Core and .NET applications, the configuration file usually is in JSON-format and is called `appsettings.json`. The configuration of connection strings section is explained in the following documentation article: [How to Host Reports Service in ASP.NET Core in .NET {{site.mindotnetversion}}]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-in-.net-6-with-minimal-api%}). When the connection string is stored in the configuration file, you need to specify the name of the configuration element as a value for the `ConnectionString` property of `SqlDataSource`. Specifying a value for the `ProviderName` property is no longer necessary, since that information is already present in the configuration element itself. diff --git a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md index 20cb86367..31f8e7a21 100644 --- a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md +++ b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md @@ -21,7 +21,7 @@ The Standalone Report Designer is distributed as a single EXE file, which simpli Since its introduction in 2013 R2, the Standalone Report Designer is built against `.NET Framework 4.6.2` 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. -Starting with [R3 2022 (16.2.22.914)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2022-16-2-22-914), 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 (18.0.24.130)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2024-q1-18-0-24-130) 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. +Starting with [R3 2022 (16.2.22.914)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2022-16-2-22-914), a new version of Standalone Report Designer is available. It is named Telerik.ReportDesigner.Net and targets .NET {{site.mindotnetversion}}. Its main purpose is to allow the report authors to load and use their assemblies compiled against .NET Standard, .NET Core, and .NET {{site.mindotnetversion}}+. 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. ## Differences between the .NET and .NET Framework designers' functionality diff --git a/doc-output/configure-the-report-engine/processing-element.md b/doc-output/configure-the-report-engine/processing-element.md index b8a40930b..05324ca90 100644 --- a/doc-output/configure-the-report-engine/processing-element.md +++ b/doc-output/configure-the-report-engine/processing-element.md @@ -149,7 +149,7 @@ Skia implementation is not available in applications that target .NET Framework. | | | | ------ | ------ | -|Attributes| __engineName__ – required string attribute. Determines the type of the [Telerik.Drawing.Contract.GraphicsEngine](/api/Telerik.Drawing.Contract.GraphicsEngine) used in the application. Available values:| +|Attributes| __engineName__ – required string attribute. Determines the type of the [Telerik.Drawing.Contract.GraphicsEngine](/api/Telerik.Drawing.Contract.GraphicsEngine) used in the application. Available values:| ### ResourceResolver diff --git a/embedding-reports/asp-net-core-reporting.md b/embedding-reports/asp-net-core-reporting.md index fb2cb205a..052af75a5 100644 --- a/embedding-reports/asp-net-core-reporting.md +++ b/embedding-reports/asp-net-core-reporting.md @@ -47,7 +47,7 @@ The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/ ### Requirements -.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ### Implementation diff --git a/embedding-reports/blazor-reporting.md b/embedding-reports/blazor-reporting.md index d1406bbf7..19526e6eb 100644 --- a/embedding-reports/blazor-reporting.md +++ b/embedding-reports/blazor-reporting.md @@ -50,7 +50,7 @@ Telerik Reporting provides two Web Report Viewers suitable for Blazor Web Report ### Requirements -.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ### Implementation diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md index 78414ad0e..3ea8a0525 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md @@ -20,7 +20,7 @@ The guide is separated into sections for readability reasons. Along with the ste ## Prerequisites * [Visual Studio 2019, version 16.8+](https://www.visualstudio.com/vs/) or higher -* [NET 6 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) or higher +* [.NET {{site.mindotnetversion}} SDK](https://dotnet.microsoft.com/en-us/download/dotnet/{{site.mindotnetversion}}.0) or higher ## Using the REST Service Project Template diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md index ce616b596..08b7849f3 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md @@ -19,7 +19,7 @@ The guide is separated into sections for readability reasons. Along with the ste ## Prerequisites * [Visual Studio 2022, version 17+](https://www.visualstudio.com/vs/) -* [NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) or higher +* [.NET {{site.mindotnetversion}} SDK](https://dotnet.microsoft.com/download/dotnet/{{site.mindotnetversion}}.0) or higher ## Using the REST Service Project Template diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md index 440d39a9d..18bce2bf7 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md @@ -18,7 +18,7 @@ The guide is separated into sections for readability reasons. Along with the ste ## Prerequisites * [Visual Studio 2022, version 17+](https://www.visualstudio.com/vs/) -* [NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) or higher +* [.NET {{site.mindotnetversion}} SDK](https://dotnet.microsoft.com/download/dotnet/{{site.mindotnetversion}}.0) or higher ## Using the REST Service Project Template diff --git a/embedding-reports/overview.md b/embedding-reports/overview.md index 4ed144396..bc09802c9 100644 --- a/embedding-reports/overview.md +++ b/embedding-reports/overview.md @@ -37,7 +37,8 @@ Telerik Reporting offers numerous ways to [Display Reports in Applications]({%sl * [WinUI Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/winui-3-desktop-application/overview%}) - a composite of Telerik UI for WinUI desktop controls that is suitable for WinUI 3 projects. ### Requirements -.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. + +The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ## Adding the Report Engine diff --git a/embedding-reports/spa-reporting.md b/embedding-reports/spa-reporting.md index db4f13495..7b1851cd4 100644 --- a/embedding-reports/spa-reporting.md +++ b/embedding-reports/spa-reporting.md @@ -62,7 +62,7 @@ The Telerik Reporting product comes with ready-to-use Report Viewers for the fol ### Requirements -.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ### Implementation From 1569c3fa026afa86a0762c0039dbc6865212f20c Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Fri, 13 Jun 2025 23:58:04 +0300 Subject: [PATCH 2/6] docs: update undefined not iterable article --- ...ik-reportviewer-typeerror-undefined-is-not-iterable.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md b/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md index 860849144..a93472aa8 100644 --- a/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md +++ b/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md @@ -1,6 +1,6 @@ --- -title: TypeError undefined is not iterable in Telerik ReportViewer -description: Resolving the 'TypeError undefined is not iterable' error when previewing a report with Telerik ReportViewer. +title: TypeError undefined is not iterable in HTML5-based report viewers +description: Learn how to resolve the 'TypeError undefined is not iterable' error when previewing a report in HTML5-based report viewers. type: troubleshooting page_title: Fix TypeError undefined is not iterable in HTML5-based report viewer slug: telerik-reportviewer-typeerror-undefined-is-not-iterable @@ -33,11 +33,11 @@ When attempting to preview a report using an HTML5-based report viewer, the foll ## Cause -This issue occurs due to a breaking change in the latest version, where the report viewer is no longer fully initialized immediately after the `$("#reportViewer1").telerik_ReportViewer` call. As a result, subsequent calls like `reportViewer.reportSource()` immediately after initialization do not behave as expected. +This issue occurs due to a breaking change in the 19.1.25.521 version, where the report viewer is no longer fully initialized immediately after the `$("#reportViewer1").telerik_ReportViewer` call. As a result, subsequent calls like `reportViewer.reportSource()` immediately after it do not behave as expected. ## Solution -Use the `ready` event to ensure the report viewer is fully initialized before setting the report source. For example, in the HTML5 report viewer, this would look as follows: +Place logic that relies on the report viewer being fully initialized, such as the `reportViewer.reportSource()` calls, inside the `ready` event instead. For example, in the [HTML5 report viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}), this would look as follows: ````javascript $("#reportViewer1") From f44cee776571284f1443807ca555b4f730861ea8 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Sat, 14 Jun 2025 00:05:09 +0300 Subject: [PATCH 3/6] revert changes --- .../connecting-the-sqldatasource-component-to-a-data-source.md | 2 +- .../desktop-designers/standalone-report-designer/overview.md | 2 +- doc-output/configure-the-report-engine/processing-element.md | 2 +- embedding-reports/asp-net-core-reporting.md | 2 +- embedding-reports/blazor-reporting.md | 2 +- .../host-reports-service-in-.net-6-with-minimal-api.md | 2 +- .../host-reports-service-in-.net-with-controllers.md | 2 +- embedding-reports/overview.md | 3 +-- embedding-reports/spa-reporting.md | 2 +- 9 files changed, 9 insertions(+), 10 deletions(-) diff --git a/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md b/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md index 69a339798..48559bc56 100644 --- a/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md +++ b/designing-reports/connecting-to-data/data-source-components/sqldatasource-component/connecting-the-sqldatasource-component-to-a-data-source.md @@ -30,7 +30,7 @@ The following example shows how to connect to the __SQL Server AdventureWorks__ ```` -Configuration files in XML format are used in .NET Framework applications. In .NET Core and .NET applications, the configuration file usually is in JSON-format and is called `appsettings.json`. The configuration of connection strings section is explained in the following documentation article: [How to Host Reports Service in ASP.NET Core in .NET {{site.mindotnetversion}}]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-in-.net-6-with-minimal-api%}). +Configuration files in XML format are used in .NET Framework applications. In .NET Core and .NET 6+ applications, the configuration file usually is in JSON-format and is called `appsettings.json`. The configuration of connection strings section is explained in the following documentation article: [How to Host Reports Service in ASP.NET Core in .NET {{site.mindotnetversion}}]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-in-.net-6-with-minimal-api%}). When the connection string is stored in the configuration file, you need to specify the name of the configuration element as a value for the `ConnectionString` property of `SqlDataSource`. Specifying a value for the `ProviderName` property is no longer necessary, since that information is already present in the configuration element itself. diff --git a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md index 31f8e7a21..20cb86367 100644 --- a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md +++ b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview.md @@ -21,7 +21,7 @@ The Standalone Report Designer is distributed as a single EXE file, which simpli Since its introduction in 2013 R2, the Standalone Report Designer is built against `.NET Framework 4.6.2` 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. -Starting with [R3 2022 (16.2.22.914)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2022-16-2-22-914), a new version of Standalone Report Designer is available. It is named Telerik.ReportDesigner.Net and targets .NET {{site.mindotnetversion}}. Its main purpose is to allow the report authors to load and use their assemblies compiled against .NET Standard, .NET Core, and .NET {{site.mindotnetversion}}+. 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. +Starting with [R3 2022 (16.2.22.914)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-r3-2022-16-2-22-914), 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 (18.0.24.130)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2024-q1-18-0-24-130) 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. ## Differences between the .NET and .NET Framework designers' functionality diff --git a/doc-output/configure-the-report-engine/processing-element.md b/doc-output/configure-the-report-engine/processing-element.md index 05324ca90..b8a40930b 100644 --- a/doc-output/configure-the-report-engine/processing-element.md +++ b/doc-output/configure-the-report-engine/processing-element.md @@ -149,7 +149,7 @@ Skia implementation is not available in applications that target .NET Framework. | | | | ------ | ------ | -|Attributes| __engineName__ – required string attribute. Determines the type of the [Telerik.Drawing.Contract.GraphicsEngine](/api/Telerik.Drawing.Contract.GraphicsEngine) used in the application. Available values:
  • __PlatformDependent__ - the default value. On the Windows platform, the application will use the GDI graphics engine. On non-Windows platforms, the application will use the Skia graphics engine.
  • __Gdi__ - the application will use GDI graphics engine. On non-Windows platforms in applications that target .NET 7 or higher, this will cause runtime exceptions of type __PlatformNotSupported__ to be thrown. Can be used on Windows and non-Windows platforms in applications that target .NET {{site.mindotnetversion}} or higher framework.
| +|Attributes| __engineName__ – required string attribute. Determines the type of the [Telerik.Drawing.Contract.GraphicsEngine](/api/Telerik.Drawing.Contract.GraphicsEngine) used in the application. Available values:
  • __PlatformDependent__ - the default value. On the Windows platform, the application will use the GDI graphics engine. On non-Windows platforms, the application will use the Skia graphics engine.
  • __Gdi__ - the application will use GDI graphics engine. On non-Windows platforms in applications that target .NET 7 or higher, this will cause runtime exceptions of type __PlatformNotSupported__ to be thrown. For .NET 6 and lower frameworks, this setting will require installing __libgdiplus__ library that handles GDI calls.
  • __Skia__ - the application will use the Skia graphics engine through the SkiaSharp implementation. Can be used on Windows and non-Windows platforms in applications that target .NET 6 or higher framework.
| ### ResourceResolver diff --git a/embedding-reports/asp-net-core-reporting.md b/embedding-reports/asp-net-core-reporting.md index 052af75a5..fb2cb205a 100644 --- a/embedding-reports/asp-net-core-reporting.md +++ b/embedding-reports/asp-net-core-reporting.md @@ -47,7 +47,7 @@ The [HTML5 Report Viewer]({%slug telerikreporting/using-reports-in-applications/ ### Requirements -The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ### Implementation diff --git a/embedding-reports/blazor-reporting.md b/embedding-reports/blazor-reporting.md index 19526e6eb..d1406bbf7 100644 --- a/embedding-reports/blazor-reporting.md +++ b/embedding-reports/blazor-reporting.md @@ -50,7 +50,7 @@ Telerik Reporting provides two Web Report Viewers suitable for Blazor Web Report ### Requirements -The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ### Implementation diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md index 08b7849f3..ce616b596 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md @@ -19,7 +19,7 @@ The guide is separated into sections for readability reasons. Along with the ste ## Prerequisites * [Visual Studio 2022, version 17+](https://www.visualstudio.com/vs/) -* [.NET {{site.mindotnetversion}} SDK](https://dotnet.microsoft.com/download/dotnet/{{site.mindotnetversion}}.0) or higher +* [NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) or higher ## Using the REST Service Project Template diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md index 18bce2bf7..440d39a9d 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md @@ -18,7 +18,7 @@ The guide is separated into sections for readability reasons. Along with the ste ## Prerequisites * [Visual Studio 2022, version 17+](https://www.visualstudio.com/vs/) -* [.NET {{site.mindotnetversion}} SDK](https://dotnet.microsoft.com/download/dotnet/{{site.mindotnetversion}}.0) or higher +* [NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) or higher ## Using the REST Service Project Template diff --git a/embedding-reports/overview.md b/embedding-reports/overview.md index bc09802c9..4ed144396 100644 --- a/embedding-reports/overview.md +++ b/embedding-reports/overview.md @@ -37,8 +37,7 @@ Telerik Reporting offers numerous ways to [Display Reports in Applications]({%sl * [WinUI Report Viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/winui-3-desktop-application/overview%}) - a composite of Telerik UI for WinUI desktop controls that is suitable for WinUI 3 projects. ### Requirements - -The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ## Adding the Report Engine diff --git a/embedding-reports/spa-reporting.md b/embedding-reports/spa-reporting.md index 7b1851cd4..db4f13495 100644 --- a/embedding-reports/spa-reporting.md +++ b/embedding-reports/spa-reporting.md @@ -62,7 +62,7 @@ The Telerik Reporting product comes with ready-to-use Report Viewers for the fol ### Requirements -The [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization), available in .NET, restricts the application to use only invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. +.NET 6 introduced a [globalization-invariant mode](https://learn.microsoft.com/en-us/dotnet/core/runtime-config/globalization) which, if enabled, does not allow the creation of any culture except the invariant culture. The Report Engine relies on instantiating cultures to support localization, formatting, and unit conversion, so enabling invariant globalization will break the engine's functionality. Refer to the [Only invariant culture is supported in globalization-invariant mode]({%slug only-invariant-culture-is-supported-in-globalization-invariant-mode-error%}) article for instructions on how to disable the `Invariant Globalization` mode. ### Implementation From f7ec15c532ff8190a8728f6999bf6247aa5bc481 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Sat, 14 Jun 2025 00:06:27 +0300 Subject: [PATCH 4/6] revert --- .../host-reports-service-in-.net-5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md index 3ea8a0525..78414ad0e 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md @@ -20,7 +20,7 @@ The guide is separated into sections for readability reasons. Along with the ste ## Prerequisites * [Visual Studio 2019, version 16.8+](https://www.visualstudio.com/vs/) or higher -* [.NET {{site.mindotnetversion}} SDK](https://dotnet.microsoft.com/en-us/download/dotnet/{{site.mindotnetversion}}.0) or higher +* [NET 6 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) or higher ## Using the REST Service Project Template From a96059be6aafa5744d26d8cbd27d985b73338b9a Mon Sep 17 00:00:00 2001 From: Petar Todorov <109748926+petar-i-todorov@users.noreply.github.com> Date: Mon, 16 Jun 2025 17:37:16 +0300 Subject: [PATCH 5/6] Update knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- .../telerik-reportviewer-typeerror-undefined-is-not-iterable.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md b/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md index a93472aa8..50f608b45 100644 --- a/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md +++ b/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md @@ -33,7 +33,7 @@ When attempting to preview a report using an HTML5-based report viewer, the foll ## Cause -This issue occurs due to a breaking change in the 19.1.25.521 version, where the report viewer is no longer fully initialized immediately after the `$("#reportViewer1").telerik_ReportViewer` call. As a result, subsequent calls like `reportViewer.reportSource()` immediately after it do not behave as expected. +This issue occurs due to a breaking change in the 19.1.25.521 version, where the report viewer is no longer fully initialized immediately after the `$("#reportViewer1").telerik_ReportViewer` call. As a result, subsequent calls like `reportViewer.reportSource()` will fail because the viewer instance is not yet ready. ## Solution From 30075242d763bb37449d33139cf5e4d38b2c6401 Mon Sep 17 00:00:00 2001 From: petar-i-todorov Date: Mon, 16 Jun 2025 18:53:22 +0300 Subject: [PATCH 6/6] docs: make it more technically accurate --- .../telerik-reportviewer-typeerror-undefined-is-not-iterable.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md b/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md index 50f608b45..79585ff46 100644 --- a/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md +++ b/knowledge-base/telerik-reportviewer-typeerror-undefined-is-not-iterable.md @@ -37,7 +37,7 @@ This issue occurs due to a breaking change in the 19.1.25.521 version, where the ## Solution -Place logic that relies on the report viewer being fully initialized, such as the `reportViewer.reportSource()` calls, inside the `ready` event instead. For example, in the [HTML5 report viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}), this would look as follows: +Place logic that relies on the report viewer being fully initialized, such as the `reportViewer.reportSource()` calls, inside the `ready` event handler instead. For example, in the [HTML5 report viewer]({%slug telerikreporting/using-reports-in-applications/display-reports-in-applications/web-application/html5-report-viewer/overview%}), this would look as follows: ````javascript $("#reportViewer1")