diff --git a/_config.yml b/_config.yml index 3667892f2..abc2e40c3 100644 --- a/_config.yml +++ b/_config.yml @@ -476,7 +476,7 @@ kendothemeversion: "10.2.0" blazoruiversion: "9.1.0" mindotnetversion: "8" mindotnetoutputdir: "\\bin\\Debug\\net8.0" -dotnetversions: ".NET 8 and .NET 9" +dotnetversions: ".NET 8, .NET 9 and .NET 10" # Feedback Form Product code productCode: REPORTING diff --git a/designing-reports/connecting-to-data/data-source-components/objectdatasource-component/connecting-the-objectdatasource-component-to-a-data-source.md b/designing-reports/connecting-to-data/data-source-components/objectdatasource-component/connecting-the-objectdatasource-component-to-a-data-source.md index 707f28857..72976b286 100644 --- a/designing-reports/connecting-to-data/data-source-components/objectdatasource-component/connecting-the-objectdatasource-component-to-a-data-source.md +++ b/designing-reports/connecting-to-data/data-source-components/objectdatasource-component/connecting-the-objectdatasource-component-to-a-data-source.md @@ -26,7 +26,7 @@ When you configure the ObjectDataSource component the settings below are obligat Framework 4.0__. For that reason, it cannot load and resolve classes from assemblies built against .NET Standard 2.1 or .NET {{site.mindotnetversion}}+. You can see the [.NET Standard compatibility chart](https://learn.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0) which explains how and when the assemblies can be loaded in different framework versions. - >The new [.NET Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}#starting-the-standalone-report-designer-for-net) is built for .NET 8 and can resolve assemblies built with `.NET Standard`, `.NET {{site.mindotnetversion}}` and later. + >The new [.NET Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}#starting-the-standalone-report-designer-for-net) is built for .NET 10 and can resolve assemblies built with `.NET Standard`, `.NET {{site.mindotnetversion}}` and later. 1. Add the following piece of code from [Bind to a BusinessObject]({%slug telerikreporting/designing-reports/connecting-to-data/data-source-components/objectdatasource-component/how-to/how-to-bind-to-a-businessobject%}). diff --git a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/overview.md b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/overview.md index c4b110ed2..5d92cf95f 100644 --- a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/overview.md +++ b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/overview.md @@ -133,7 +133,7 @@ The following code example shows the default `Telerik.ReportDesigner.exe.config` ```` -## Default Configuration for the .NET 8 Standalone Report Designer +## Default Configuration for the .NET 10 Standalone Report Designer The following code example shows the default `Telerik.ReportDesigner.Net.dll.config` file that is distributed with the Report Designer for .NET. A major difference with the designer for .NET Framework is that the Trace Listener for .NET is in the `Telerik.Reporting` section rather than in the `system.diagnostics` section as in .NET Framework. diff --git a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/srd-net-working-with-type-report-definitions.md b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/srd-net-working-with-type-report-definitions.md index 02815410f..f4aa428c6 100644 --- a/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/srd-net-working-with-type-report-definitions.md +++ b/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/srd-net-working-with-type-report-definitions.md @@ -31,7 +31,7 @@ The designer's functionality for working with Coded Reports relies on [MSBuild]( If you have Visual Studio 2017 or newer installed, the required MSBuild version will be available out of the box. > The .NET SDK corresponding to your project’s target framework must also be installed. -For example, if your report library targets .NET 8, ensure the .NET 8 SDK is present. +For example, if your report library targets .10, ensure the .NET 10 SDK is present. Without it, SRD.NET will fail to compile the project. ## Opening Coded Reports diff --git a/designing-reports/report-designer-tools/overview.md b/designing-reports/report-designer-tools/overview.md index aa870840e..ce64e3c9b 100644 --- a/designing-reports/report-designer-tools/overview.md +++ b/designing-reports/report-designer-tools/overview.md @@ -17,9 +17,9 @@ This document gives a brief overview of the available Report Designers. ## Standalone Report Designer -[Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) is a standalone desktop application that features an easy-to-use environment. It is available for the .NET Framework and .NET 8: +[Standalone Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}) is a standalone desktop application that features an easy-to-use environment. It is available for the .NET Framework and .NET 10: -* The executable file starting the application is `Telerik.ReportDesigner.exe` for the .NET Framework and `Telerik.ReportDesigner.Net.exe` for .NET 8. By default, it will be deployed upon product installation in the '(*Telerik Reporting installation folder*)\Report Designer' folder. For example, 'C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer'. The .NET 8 version is in the '\.NET' subfolder. +* The executable file starting the application is `Telerik.ReportDesigner.exe` for the .NET Framework and `Telerik.ReportDesigner.Net.exe` for .NET 10. By default, it will be deployed upon product installation in the '(*Telerik Reporting installation folder*)\Report Designer' folder. For example, 'C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}\Report Designer'. The .NET 10 version is in the '\.NET' subfolder. * Does not require Visual Studio; * Works with XML report definitions packaged in a zip archive `.TRDP` or in the plain legacy format `.TRDX`: diff --git a/getting-started/installation/dot-net-core-support.md b/getting-started/installation/dot-net-core-support.md index 77f006087..0f5db27a8 100644 --- a/getting-started/installation/dot-net-core-support.md +++ b/getting-started/installation/dot-net-core-support.md @@ -1,7 +1,7 @@ --- title: .NET Support page_title: Using Telerik Reporting with .NET or .NET Standard -description: "Learn how to use Telerik Reporting in .NET 8/9 or .NET Standard applications on Windows, Linux, and macOS platforms and how to deploy them in Docker images." +description: "Learn how to use Telerik Reporting in .NET 8+ or .NET Standard applications on Windows, Linux, and macOS platforms and how to deploy them in Docker images." slug: telerikreporting/using-reports-in-applications/dot-net-core-support previous_url: /using-reports-in-applications/dot-net-core-support, /use-reports-in-net-core-apps tags: telerik, reporting, dotnet, core, support, getting, started, download, and, installation diff --git a/getting-started/installation/included-assemblies.md b/getting-started/installation/included-assemblies.md index c13a571ce..dd5b7de45 100644 --- a/getting-started/installation/included-assemblies.md +++ b/getting-started/installation/included-assemblies.md @@ -18,7 +18,7 @@ The assemblies come sorted in several folders so that you can use the ones you n * If you target `.NET Framework`, use the assemblies from the `Bin` folder. * If you target `.NET Standard`, use the assemblies from the `\Bin\netstandard2.0` folder. -* If you target `.NET 8`, use the assemblies from the `\Bin\net8.0` and `\Bin\net8.0-windows` folders. +* If you target `.NET 8` or later, use the assemblies from the `\Bin\net8.0` and `\Bin\net8.0-windows` folders. ## Main Assemblies diff --git a/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net.md b/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net.md index 2b713c9e3..e8e45341b 100644 --- a/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net.md +++ b/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net.md @@ -27,6 +27,8 @@ res_type: kb ## Description +> From Q4 2025, the Standalone Report Designer for .NET is built with .NET 10 + This article describes How to load `.NET 9` assemblies in the Standalone Report Designer for .NET *(**SRD.NET** for short)*. It is important to state that SRD.NET is targeting **.NET 8** instead of .NET 9 because .NET 8 is a **Major** release while .NET 9 is not. Major releases happen once a year, even-numbered versions are the long-term supported (LTS) releases. diff --git a/knowledge-base/only-invariant-culture-is-supported-in-globalization-invariant-mode-error.md b/knowledge-base/only-invariant-culture-is-supported-in-globalization-invariant-mode-error.md index ef56c5f36..f0a0133fd 100644 --- a/knowledge-base/only-invariant-culture-is-supported-in-globalization-invariant-mode-error.md +++ b/knowledge-base/only-invariant-culture-is-supported-in-globalization-invariant-mode-error.md @@ -4,7 +4,7 @@ description: "Learn how to resolve the error message 'Only invariant culture is type: troubleshooting page_title: Only invariant culture is supported in globalization-invariant mode slug: only-invariant-culture-is-supported-in-globalization-invariant-mode-error -tags: .NET 6, .NET 7, .NET 8, .NET 9 +tags: .NET 7, .NET 8, .NET 9, and .NET 10 res_type: kb --- diff --git a/knowledge-base/pdf-rendering-not-available-telerik-reporting.md b/knowledge-base/pdf-rendering-not-available-telerik-reporting.md index 17dc5a9ab..20dc490c4 100644 --- a/knowledge-base/pdf-rendering-not-available-telerik-reporting.md +++ b/knowledge-base/pdf-rendering-not-available-telerik-reporting.md @@ -26,7 +26,7 @@ ticketid: 1659555 ## Description -After upgrading an ASP.NET Core application to .NET 8 the PDF rendering format becomes unavailable. The error message encountered is `Telerik.Reporting.Processing.RendererNotAvailableException: PDF rendering format is not available`. +After upgrading an ASP.NET Core application to .NET 8+ the PDF rendering format becomes unavailable. The error message encountered is `Telerik.Reporting.Processing.RendererNotAvailableException: PDF rendering format is not available`. ## Cause diff --git a/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core.md b/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core.md index eaa163faa..5ea2d994c 100644 --- a/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core.md +++ b/knowledge-base/use-reporting-in-dotnetcore-with-entity-framework-core.md @@ -39,7 +39,7 @@ Use an `ObjectDataSource` component instead, which supports the [Entity Framewor - Standalone Report Designer for .NET - The [Standalone Report Designer for .NET]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}#starting-the-standalone-report-designer-for-net) is built on `.NET 8` and can thus resolve assemblies built targeting .NET Core up to .NET 8, or .NET Standard. + The [Standalone Report Designer for .NET]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/overview%}#starting-the-standalone-report-designer-for-net) is built on `.NET 10` and can thus resolve assemblies built targeting .NET Core up to .NET 10, or .NET Standard. It is necessary to register the assembly in the designer's configuration file as explained in the [Extending Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/standalone-report-designer/configuration/extending-report-designer%}) article.