telerik · petar-i-todorov · Jun 16, 2025 · Jun 12, 2025 · Jun 13, 2025 · Jun 13, 2025
diff --git a/...datasource-component/connecting-the-sqldatasource-component-to-a-data-source.md b/...datasource-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>
 ````
 
-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%}).
+.NET Framework applications use configuration files in XML format, while .NET Core and .NET applications usually have a JSON-based configuration file, called `appsettings.json`. The configuration of the connection strings section in .NET 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/.../report-designer-tools/desktop-designers/standalone-report-designer/overview.md b/.../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 the Standalone Report Designer is available. It is named Telerik.ReportDesigner.Net and targets .NET {{site.mindotnetversion}}. Its main purpose is to allow 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
@@ -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:<ul><li>__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.</li><li>__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.</li><li>__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.</li></ul>|
+|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:<ul><li>__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.</li><li>__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.</li></ul>|
 
 
 ### ResourceResolver

diff --git 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 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
@@ -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 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/...-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-5.md b/...-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/...-core-web-api-implementation/host-reports-service-in-.net-6-with-minimal-api.md b/...-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/...et-core-web-api-implementation/host-reports-service-in-.net-with-controllers.md b/...et-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
@@ -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 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
@@ -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 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