From c2a1f9bf6fa79ef1e2ca1d26312d400d2975f541 Mon Sep 17 00:00:00 2001 From: Dess Date: Tue, 15 Apr 2025 21:00:58 +0300 Subject: [PATCH 01/11] Update how-to-remove-trial-message.md --- knowledge-base/how-to-remove-trial-message.md | 20 ++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/knowledge-base/how-to-remove-trial-message.md b/knowledge-base/how-to-remove-trial-message.md index d4e00745e..002ddcfc7 100644 --- a/knowledge-base/how-to-remove-trial-message.md +++ b/knowledge-base/how-to-remove-trial-message.md @@ -11,19 +11,16 @@ res_type: kb ## Environment - - - - - - - -
ProductProgress® Telerik® Reporting
+| Version | Product | +| ---- | ---- | ---- | +| Valid until Q2 2025 | Telerik Reporting | ## Description This tutorial explains in detail how to upgrade your Telerik [Trial]({%slug telerikreporting/licensing%}) to a Licensed version of [Telerik Reporting](https://www.telerik.com/account/product-download?product=REPORTING). +>caution This approach is valid for versions **before Q2 2025**. For later versions, it is just necessary to update the [license key]({%slug setting-up-license-key%}). + Let's start with having a trial version installed on your machine and a project that uses the trial version. Access to the Trial version of product files in the Downloads section of your Telerik account: ![Downloads Trial](images/downloads-section-trial-license.png) @@ -71,4 +68,9 @@ For additional details, you may also check the [Upgrading Trial to Purchase]({%s 1. Install the respective Purchase version of the NuGet packages, without the word "Trial" in its name: - ![Install Licensed Package](images/install-dev-package.png) + ![Install Licensed Package](images/install-dev-package.png) + + +## See Also + +* [Telerik Reporting Licensing before 2025]({%slug telerikreporting/licensing%}) From b584637aacf8d7ce4468da04c9494b1f02f1c3e7 Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Tue, 15 Apr 2025 21:05:09 +0300 Subject: [PATCH 02/11] Update how-to-remove-trial-message.md --- knowledge-base/how-to-remove-trial-message.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/how-to-remove-trial-message.md b/knowledge-base/how-to-remove-trial-message.md index 002ddcfc7..cd99a28e3 100644 --- a/knowledge-base/how-to-remove-trial-message.md +++ b/knowledge-base/how-to-remove-trial-message.md @@ -19,7 +19,7 @@ res_type: kb This tutorial explains in detail how to upgrade your Telerik [Trial]({%slug telerikreporting/licensing%}) to a Licensed version of [Telerik Reporting](https://www.telerik.com/account/product-download?product=REPORTING). ->caution This approach is valid for versions **before Q2 2025**. For later versions, it is just necessary to update the [license key]({%slug setting-up-license-key%}). +>caution This approach is valid for versions [before Q2 2025]({%slug telerikreporting/licensing%}). For later versions, it is just necessary to update the [license key]({%slug setting-up-license-key%}). Let's start with having a trial version installed on your machine and a project that uses the trial version. Access to the Trial version of product files in the Downloads section of your Telerik account: From 3fcfb332c6bb9cd3b6d5b5983f385fdb163e0eef Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Tue, 15 Apr 2025 21:10:43 +0300 Subject: [PATCH 03/11] Update how-to-remove-trial-message.md --- knowledge-base/how-to-remove-trial-message.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/how-to-remove-trial-message.md b/knowledge-base/how-to-remove-trial-message.md index cd99a28e3..f62eae4fa 100644 --- a/knowledge-base/how-to-remove-trial-message.md +++ b/knowledge-base/how-to-remove-trial-message.md @@ -12,7 +12,7 @@ res_type: kb ## Environment | Version | Product | -| ---- | ---- | ---- | +| ---- | ---- | | Valid until Q2 2025 | Telerik Reporting | ## Description From 1fe105ae07fd0bcac8cf0d19022fdf20d293e35f Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Wed, 16 Apr 2025 15:11:36 +0300 Subject: [PATCH 04/11] Move the old licensing to the KB section Recommended by Dancho to move the "Before 2025" article as a KB resource to avoid confusion. --- {licensing => knowledge-base}/before-2025.md | 4 +++- knowledge-base/how-to-remove-trial-message.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) rename {licensing => knowledge-base}/before-2025.md (90%) diff --git a/licensing/before-2025.md b/knowledge-base/before-2025.md similarity index 90% rename from licensing/before-2025.md rename to knowledge-base/before-2025.md index d63985a5b..4ce5d9d8b 100644 --- a/licensing/before-2025.md +++ b/knowledge-base/before-2025.md @@ -11,7 +11,9 @@ previous_url: /installation-trial-license-limitation # Telerik Reporting Licensing before 2025 -Telerik Reporting comes in trial and developer (or commercial) licenses. +Telerik Reporting used to come in separate **Trial** and **Developer** (or commercial) assets distribution until **Q2 2025**. + +>caution After launching the [new licensing mechanism in Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product. ## Trial Licenses diff --git a/knowledge-base/how-to-remove-trial-message.md b/knowledge-base/how-to-remove-trial-message.md index f62eae4fa..1c51f93b3 100644 --- a/knowledge-base/how-to-remove-trial-message.md +++ b/knowledge-base/how-to-remove-trial-message.md @@ -19,7 +19,7 @@ res_type: kb This tutorial explains in detail how to upgrade your Telerik [Trial]({%slug telerikreporting/licensing%}) to a Licensed version of [Telerik Reporting](https://www.telerik.com/account/product-download?product=REPORTING). ->caution This approach is valid for versions [before Q2 2025]({%slug telerikreporting/licensing%}). For later versions, it is just necessary to update the [license key]({%slug setting-up-license-key%}). +>caution This approach is valid for versions [before Q2 2025]({%slug telerikreporting/licensing%}). After launching the [new licensing mechanism](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product. Let's start with having a trial version installed on your machine and a project that uses the trial version. Access to the Trial version of product files in the Downloads section of your Telerik account: From 506803a15fd6ce5f0a3c7c3a1a8c67d0f378d5a2 Mon Sep 17 00:00:00 2001 From: Dess Date: Mon, 5 May 2025 16:47:34 +0300 Subject: [PATCH 05/11] Update knowledge-base/before-2025.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- knowledge-base/before-2025.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/before-2025.md b/knowledge-base/before-2025.md index 4ce5d9d8b..6a8cbaeb5 100644 --- a/knowledge-base/before-2025.md +++ b/knowledge-base/before-2025.md @@ -11,7 +11,7 @@ previous_url: /installation-trial-license-limitation # Telerik Reporting Licensing before 2025 -Telerik Reporting used to come in separate **Trial** and **Developer** (or commercial) assets distribution until **Q2 2025**. +Before Q2 2025, Telerik Reporting was distributed in two versions: Trial and Developer (commercial), each having its own assets. Starting with Q2 2025, Telerik Reporting comes in a unified installation package regardless of whether you have a developer (commercial) or a trial license. >caution After launching the [new licensing mechanism in Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product. From 1b7ccebe2f31c46664c324bcfecf6124a2a3dda6 Mon Sep 17 00:00:00 2001 From: Dess Date: Mon, 5 May 2025 16:48:07 +0300 Subject: [PATCH 06/11] Update knowledge-base/before-2025.md Co-authored-by: Yordan <60105689+yordan-mitev@users.noreply.github.com> --- knowledge-base/before-2025.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/before-2025.md b/knowledge-base/before-2025.md index 6a8cbaeb5..ecdc5e2f7 100644 --- a/knowledge-base/before-2025.md +++ b/knowledge-base/before-2025.md @@ -13,7 +13,7 @@ previous_url: /installation-trial-license-limitation Before Q2 2025, Telerik Reporting was distributed in two versions: Trial and Developer (commercial), each having its own assets. Starting with Q2 2025, Telerik Reporting comes in a unified installation package regardless of whether you have a developer (commercial) or a trial license. ->caution After launching the [new licensing mechanism in Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product. +>caution Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. ## Trial Licenses From 8ae2e51bd3e8b05a13356d32b53a144d8d9e60c2 Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Mon, 5 May 2025 16:50:54 +0300 Subject: [PATCH 07/11] Addressed Dancho's recommendation --- knowledge-base/how-to-remove-trial-message.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/knowledge-base/how-to-remove-trial-message.md b/knowledge-base/how-to-remove-trial-message.md index 1c51f93b3..1d2b07ee6 100644 --- a/knowledge-base/how-to-remove-trial-message.md +++ b/knowledge-base/how-to-remove-trial-message.md @@ -19,7 +19,7 @@ res_type: kb This tutorial explains in detail how to upgrade your Telerik [Trial]({%slug telerikreporting/licensing%}) to a Licensed version of [Telerik Reporting](https://www.telerik.com/account/product-download?product=REPORTING). ->caution This approach is valid for versions [before Q2 2025]({%slug telerikreporting/licensing%}). After launching the [new licensing mechanism](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), the activation is performed through a [license key]({%slug setting-up-license-key%}) (trial or commercial). Upgrading from a Trial to Developer (or commercial) version requires only updating the license key without the necessity of reinstalling the respective Telerik product. +>caution Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. Let's start with having a trial version installed on your machine and a project that uses the trial version. Access to the Trial version of product files in the Downloads section of your Telerik account: From 68308b870bc3768ef77f54028978210553e26999 Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Tue, 13 May 2025 19:10:10 +0300 Subject: [PATCH 08/11] Trial vs Dev updates --- .../how-to-set-up-in-blazor-application.md | 4 ++-- .../how-to-use-blazor-report-viewer.md | 6 +++--- .../how-to-use-native-blazor-report-viewer.md | 18 +++++++++--------- .../host-reports-service-in-.net-5.md | 4 ++-- ...ports-service-in-.net-6-with-minimal-api.md | 4 ++-- ...reports-service-in-.net-core-2.1-and-2.2.md | 4 ++-- ...reports-service-in-.net-with-controllers.md | 4 ++-- ...host-reports-service-in-asp.net-core-3.1.md | 4 ++-- .../installation/installation-approaches.md | 2 +- knowledge-base/latest-internal-builds.md | 9 +++------ licensing/license-errors-and-warnings.md | 7 +++---- ...ng-up-your-telerik-reporting-license-key.md | 5 ----- 12 files changed, 31 insertions(+), 40 deletions(-) diff --git a/designing-reports/report-designer-tools/web-report-designer/how-to-set-up-in-blazor-application.md b/designing-reports/report-designer-tools/web-report-designer/how-to-set-up-in-blazor-application.md index b18f48f8c..9d00cccb1 100644 --- a/designing-reports/report-designer-tools/web-report-designer/how-to-set-up-in-blazor-application.md +++ b/designing-reports/report-designer-tools/web-report-designer/how-to-set-up-in-blazor-application.md @@ -110,8 +110,8 @@ using Microsoft.AspNetCore.Mvc; ````HTML - @* Or this one if using the Telerik.WebReportDesigner.Blazor.Trial package *@ - @**@ + @* Or this one if using the Telerik.WebReportDesigner.Blazor package *@ + @**@ ```` diff --git a/embedding-reports/display-reports-in-applications/web-application/blazor-report-viewer/how-to-use-blazor-report-viewer.md b/embedding-reports/display-reports-in-applications/web-application/blazor-report-viewer/how-to-use-blazor-report-viewer.md index 87ac0fea5..0cd2bde55 100644 --- a/embedding-reports/display-reports-in-applications/web-application/blazor-report-viewer/how-to-use-blazor-report-viewer.md +++ b/embedding-reports/display-reports-in-applications/web-application/blazor-report-viewer/how-to-use-blazor-report-viewer.md @@ -36,7 +36,7 @@ If you wish to connect the Report Viewer to a Report Server instance, refer to t ## Adding the Blazor Report Viewer component manually -1. Add NuGet package reference to the `Telerik.ReportViewer.Blazor` (or `Telerik.ReportViewer.Blazor.Trial`) package hosted on the Progress Telerik proprietary NuGet feed. Make sure you have the needed NuGet feed added to the Visual Studio setting using the article [How to add the Telerik private NuGet feed to Visual Studio]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}). +1. Add NuGet package reference to the `Telerik.ReportViewer.Blazor` package hosted on the Progress Telerik proprietary NuGet feed. Make sure you have the needed NuGet feed added to the Visual Studio setting using the article [How to add the Telerik private NuGet feed to Visual Studio]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}). 1. Make sure app configuration inside the `Configure` method of the `Startup.cs`(or `Program.cs` if .NET 6+ is used) can serve static files: @@ -74,8 +74,8 @@ app.UseStaticFiles(); ````HTML - @* Or this one if using the Telerik.ReportViewer.Blazor.Trial package *@ - @**@ + @* Or this one if using the Telerik.ReportViewer.Blazor package *@ + @**@ ```` diff --git a/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-native-blazor-report-viewer.md b/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-native-blazor-report-viewer.md index 6ebb7cfef..78bc18822 100644 --- a/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-native-blazor-report-viewer.md +++ b/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-native-blazor-report-viewer.md @@ -33,7 +33,7 @@ If you wish to connect the Report Viewer to a Report Server instance, refer to t ## Adding the Native Blazor Report Viewer Component Manually -1. Add NuGet package reference to the __Telerik.ReportViewer.BlazorNative__ (or __Telerik.ReportViewer.BlazorNative.Trial__) package hosted on the Progress Telerik proprietary NuGet feed. Make sure you have the needed NuGet feed added to the VS setting using the article [How to add the Telerik private NuGet feed to Visual Studio]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}). +1. Add NuGet package reference to the __Telerik.ReportViewer.BlazorNative__ package hosted on the Progress Telerik proprietary NuGet feed. Make sure you have the needed NuGet feed added to the VS setting using the article [How to add the Telerik private NuGet feed to Visual Studio]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}). 1. Make sure app configuration inside the `Configure` method of the `Startup.cs` (or `Program.cs` if .NET 6+ with Top Level Statements is used) file can serve static files: @@ -47,24 +47,24 @@ app.UseStaticFiles(); ````HTML - @* Or this one if using the Telerik.UI.for.Blazor.Trial package *@ - @* *@ + @* Or this one if using the Telerik.UI.for.Blazor package *@ + @* *@ - @* Or this one if using the Telerik.ReportViewer.BlazorNative.Trial package *@ - @* *@ + @* Or this one if using the Telerik.ReportViewer.BlazorNative package *@ + @* *@ @* The version of the Kendo Utils should be updated according to the version of the Kendo theme used by the Telerik UI for Blazor package. *@ @* The version of the Kendo Theme can be seen in the release notes of the Telerik UI for Blazor version - https://www.telerik.com/support/whats-new/blazor-ui/release-history. *@ - @* Or this one if using the Telerik.UI.for.Blazor.Trial package *@ - @* *@ + @* Or this one if using the Telerik.UI.for.Blazor package *@ + @* *@ - @* Or this one if using the Telerik.ReportViewer.BlazorNative.Trial package *@ - @* *@ + @* Or this one if using the Telerik.ReportViewer.BlazorNative package *@ + @* *@ ```` 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 370f0570f..05a3bbecd 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 @@ -57,8 +57,8 @@ In this tutorial, the resulting service will use the sample report definitions d This guide applies the recommended NuGet package references approach to add the dependencies: -1. Reference the __Telerik.Reporting.Services.AspNetCore__ (or __Telerik.Reporting.Services.AspNetCore.Trial__) package. -1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX, and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ (or __Telerik.Reporting.OpenXmlRendering.Trial__) NuGet package. +1. Reference the __Telerik.Reporting.Services.AspNetCore__ package. +1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX, and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ NuGet package. > The recommended way of adding the necessary dependencies is to use the [Progress Telerik proprietary NuGet feed]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}) and reference the dependencies as NuGet packages. This would also add the indirect dependencies to your project bringing easier dependency management. Alternatively, the assemblies are available in the `\Bin\net6.0\` and `\Bin\netstandard2.0\` folders of the Telerik Reporting installation directory. However, this would require to manually add all indirect dependencies listed in [.NET Support - Requirements]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}#requirements) section and also the following dependency package: [Microsoft.AspNetCore.Mvc.NewtonsoftJson version 5.0.0](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.NewtonsoftJson/) and [DocumentFormat.OpenXML version 2.7.2.0 or above](https://www.nuget.org/packages/DocumentFormat.OpenXml/). 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 c18392b63..8f2afbda7 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 @@ -57,8 +57,8 @@ In this tutorial, the resulting service will use the sample report definitions d This guide applies the recommended NuGet package references approach to add the dependencies: -1. Reference the __Telerik.Reporting.Services.AspNetCore__ (or __Telerik.Reporting.Services.AspNetCore.Trial__) package. -1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ (or __Telerik.Reporting.OpenXmlRendering.Trial__) NuGet package. +1. Reference the __Telerik.Reporting.Services.AspNetCore__ package. +1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ NuGet package. > The recommended way of adding the necessary dependencies is to use the [Progress Telerik proprietary NuGet feed]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}) and reference the dependencies as NuGet packages. This would also add the indirect dependencies to your project bringing easier dependency management. Alternatively, the assemblies are available in the `\Bin\net6.0\` and `\Bin\netstandard2.0\` folders of Telerik Reporting installation directory. However, this would require to manually add all indirect dependencies listed in [.NET Support - Requirements]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}#requirements) section and also the following dependency package: [Microsoft.AspNetCore.Mvc.NewtonsoftJson version 5.0.0](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.NewtonsoftJson/) and [DocumentFormat.OpenXML version 2.7.2.0 or above](https://www.nuget.org/packages/DocumentFormat.OpenXml/). diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-core-2.1-and-2.2.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-core-2.1-and-2.2.md index c28edc25d..59a54ca6d 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-core-2.1-and-2.2.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/host-reports-service-in-.net-core-2.1-and-2.2.md @@ -45,8 +45,8 @@ In this tutorial, the resulting service will use the sample report definitions d This guide applies the recommended NuGet package references approach to add the dependencies: -1. Reference the __Telerik.Reporting.Services.AspNetCore__ (or __Telerik.Reporting.Services.AspNetCore.Trial__) package. -1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ (or __Telerik.Reporting.OpenXmlRendering.Trial__) NuGet package. +1. Reference the __Telerik.Reporting.Services.AspNetCore__ package. +1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ NuGet package. > The Telerik Reporting engine and services assemblies are built against __.NET Standard 2.0 framework__ where applicable, which ensures compatibility with a greater variety of frameworks and applications. The recommended way of adding the necessary dependencies is to use the [Progress Telerik proprietary NuGet feed]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}) and reference the dependencies as NuGet packages. This would also add all indirect dependencies to your project bringing easier dependency management. Alternatively, the assemblies are available in the `\Bin\netstandard2.0\` folder of Telerik Reporting installation directory. However, this would require to manually add all indirect dependencies listed in [.NET Core Support - Requirements]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}#requirements) section and also the following dependency package: [DocumentFormat.OpenXML version 2.7.2.0 or above](https://www.nuget.org/packages/DocumentFormat.OpenXml/). Note that you need the last reference only to enable the Office OpenXML document formats. The Reporting engine relies on the GDI+ API which is available on the Windows OS. On Linux and macOS we use library called [libgdiplus](https://www.mono-project.com/docs/gui/libgdiplus/) instead. The GDI+ API is required for measuring, laying out, rendering the text glyphs and images. 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 c953b9059..6da13ea25 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 @@ -56,8 +56,8 @@ In this tutorial, the resulting service will use the sample report definitions d This guide applies the recommended NuGet package references approach to add the dependencies: -1. Reference the __Telerik.Reporting.Services.AspNetCore__ (or __Telerik.Reporting.Services.AspNetCore.Trial__) package. -1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ (or __Telerik.Reporting.OpenXmlRendering.Trial__) NuGet package. +1. Reference the __Telerik.Reporting.Services.AspNetCore__ package. +1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ NuGet package. > The recommended way of adding the necessary dependencies is to use the [Progress Telerik proprietary NuGet feed]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}) and reference the dependencies as NuGet packages. This would also add the indirect dependencies to your project bringing easier dependency management. Alternatively, the assemblies are available in the `\Bin\net6.0\` and `\Bin\netstandard2.0\` folders of Telerik Reporting installation directory. However, this would require to manually add all indirect dependencies listed in [.NET Support - Requirements]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}#requirements) section and also the following dependency package: [Microsoft.AspNetCore.Mvc.NewtonsoftJson version 5.0.0](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.NewtonsoftJson/) and [DocumentFormat.OpenXML version 2.7.2.0 or above](https://www.nuget.org/packages/DocumentFormat.OpenXml/). diff --git a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-3.1.md b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-3.1.md index d8befcf9d..168f09feb 100644 --- a/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-3.1.md +++ b/embedding-reports/host-the-report-engine-remotely/asp.net-core-web-api-implementation/how-to-host-reports-service-in-asp.net-core-3.1.md @@ -55,8 +55,8 @@ In this tutorial, the resulting service will use the sample report definitions d This guide applies the recommended NuGet package references approach to add the dependencies: -1. Reference the __Telerik.Reporting.Services.AspNetCore__ (or __Telerik.Reporting.Services.AspNetCore.Trial__) package. -1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ (or __Telerik.Reporting.OpenXmlRendering.Trial__) NuGet package. +1. Reference the __Telerik.Reporting.Services.AspNetCore__ package. +1. Optionally, to enable the Office OpenXML document formats (XLSX, DOCX and PPTX) as export options, reference the __Telerik.Reporting.OpenXmlRendering__ NuGet package. > The recommended way of adding the necessary dependencies is to use the [Progress Telerik proprietary NuGet feed]({%slug telerikreporting/using-reports-in-applications/how-to-add-the-telerik-private-nuget-feed-to-visual-studio%}) and reference the dependencies as NuGet packages. This would also add the indirect dependencies to your project bringing easier dependency management. Alternatively, the assemblies are available in the `\Bin\netcoreapp3.1\` folder of Telerik Reporting installation directory. However, this would require to manually add all indirect dependencies listed in [.NET Core Support - Requirements]({%slug telerikreporting/using-reports-in-applications/dot-net-core-support%}#requirements) section and also the following dependency package: [Microsoft.AspNetCore.Mvc.NewtonsoftJson version 5.0.0](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.NewtonsoftJson/) and [DocumentFormat.OpenXML version 2.7.2.0 or above](https://www.nuget.org/packages/DocumentFormat.OpenXml/). Note that you need the last reference only to enable the Office OpenXML document formats. The Reporting engine relies on the GDI+ API which is available on the Windows OS. On Linux and macOS we use library called [libgdiplus](https://www.mono-project.com/docs/gui/libgdiplus/) instead. The GDI+ API is required for measuring, laying out, rendering the text glyphs and images. diff --git a/getting-started/installation/installation-approaches.md b/getting-started/installation/installation-approaches.md index a769af08e..811a2f1c7 100644 --- a/getting-started/installation/installation-approaches.md +++ b/getting-started/installation/installation-approaches.md @@ -43,7 +43,7 @@ During the MSI installation process, consider the following: To install Telerik Reporting through the MSI automatic installer file: -1. Log into your [Telerik account](https://www.telerik.com/account). Click the __Downloads__ tab to view the available trial and commercial products and select __Telerik Reporting__. +1. Log into your [Telerik account](https://www.telerik.com/account). Click the __Downloads__ tab to view the available products and select __Telerik Reporting__. 1. From the next page, download the MSI installation and the documentation files and download the automatic installation MSI file. The source code is available for download only for commercial license holders. 1. When the download completes, run `Telerik_Reporting_[suiteversion].msi`. In the dialog that appears after you execute the MSI file, confirm that you have read and accepted the License Agreement. diff --git a/knowledge-base/latest-internal-builds.md b/knowledge-base/latest-internal-builds.md index 11122ba1b..3cda3bf5b 100644 --- a/knowledge-base/latest-internal-builds.md +++ b/knowledge-base/latest-internal-builds.md @@ -1,5 +1,5 @@ --- -title: Latest Internal Builds +title: Latest Internal Builds (Preview Version) description: "Learn more about the Latest Internal Builds, what is their purpose in Telerik Reporting and how to download and use them." type: troubleshooting page_title: Latest Internal Builds Explained @@ -29,15 +29,12 @@ It contains all the newest bug fixes. The purpose of the LIB is to allow the users to test the latest bug fixes. So, if you have experienced any problem with the current official distributions there is a possibility that the issue has already been addressed in the latest internal build. -## How to obtain the LIB? +## How to obtain the LIB (Preview Version)? Go to [Downloads for Progress® Telerik® Reporting](https://www.telerik.com/account/product-download?product=REPORTING) page, click on Internal Builds and look for the `.msi` containing the LIB: -`Telerik_Reporting_{VERSION}_TRIAL.msi` +`Telerik_Reporting_{VERSION}.msi` -or - -`Telerik_Reporting_{VERSION}_DEV.msi` ![Latest Internal Build Download page for Telerik Reporting with Purchase version 13.1.19.618 selected](resources/download-lib.png) diff --git a/licensing/license-errors-and-warnings.md b/licensing/license-errors-and-warnings.md index beba2e452..40f2ba3c8 100644 --- a/licensing/license-errors-and-warnings.md +++ b/licensing/license-errors-and-warnings.md @@ -11,10 +11,7 @@ position: 7 Starting with the [2025 Q1 (19.0.25.211)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2025-q1-19-0-25-211) release, using Telerik Reporting without a license or with an invalid license causes specific license warnings and errors. This article defines what an invalid license is, explains what is causing it, and describes the related license warnings and errors. -The implementation of the 2025 product licensing requirements will occur in two phases: - -* Phase 1 - Starting with the 2025 Q1 release, a missing or invalid license logs a warning in the build log and the report will show a watermark with a trial message. The trial distribution won't show the trial message when activated with a trial license. There will be no change in the commercial distribution. -* Phase 2 - Starting with the 2025 Q2 release, there will be only one distribution of the product with different licenses. A missing, expired, or invalid license will result in: +A missing, expired, or invalid license will result in: - A watermark appears on each report document page. - A warning message appearing in the build log: @@ -71,6 +68,8 @@ Using the Telerik Reporting in a project with an expired or missing license, the |`Your perpetual license is invalid.`|TKL102||You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following:
  • Renew your subscription and [download a new license key]({%slug license-key%}#downloading-the-license-key)
  • Downgrade to a Telerik Reporting version included in your perpetual license, as indicated in the message.
| |`Your trial license has expired.`|TKL105|Purchase a commercial license to continue using the product.| |`Your license is not valid for the detected product(s).`|TKL101|Review the purchase options for the listed products.
Alternatively, remove the references to the listed packages from `package.json`.| +|`Unable to locate licenses for all products`|TKL004|Your license is not valid for all Telerik and Kendo products added to your project. If you have already purchased the required license, then update your license key]({%slug license-key%}).| +|`No Telerik or Kendo UI product references detected in project`|TKL001|
  • If you use Telerik products and see this message, update the Telerik.Licensing package to version 1.4.9 or later.
  • If you do not use Telerik products, remove the Telerik.Licensing NuGet reference from your project.
| Starting with the 2025 Q2 release of Telerik Reporting, all conditions above will be treated as errors. diff --git a/licensing/setting-up-your-telerik-reporting-license-key.md b/licensing/setting-up-your-telerik-reporting-license-key.md index 67aac9eb4..33f65916a 100644 --- a/licensing/setting-up-your-telerik-reporting-license-key.md +++ b/licensing/setting-up-your-telerik-reporting-license-key.md @@ -13,11 +13,6 @@ Starting with the [2025 Q1 (19.0.25.211)](https://www.telerik.com/support/whats- An invalid license results in [errors and warnings]({%slug license-errors-and-warnings%}) during build and run-time indicators such as watermarks and banners. -The implementation of the 2025 licensing requirements will occur in two phases: - -- Phase 1 - Starting with the 2025 Q1 release, a missing or invalid license causes [warnings during build]({%slug license-errors-and-warnings%}) and trial messages in the generated report documents. The trial distributions won't show the trial message when activated with a trial license. The commercial distributions of the product do not exhibit any functional restrictions. -- Phase 2 - Starting with the 2025 Q2 release, there will be only one product distribution with different licenses. A missing or invalid license will result in [build errors and run-time indicators]({%slug license-errors-and-warnings%}), such as watermarks. - Note that future updates of the product may restrict or disable some features when no valid license is present. You can send us feedback through the _Contact Us_ form or by [opening a support ticket](https://www.telerik.com/account/support-center/contact-us?utm_source=licensing&utm_medium=console&utm_campaign=no_references). ## Licensing Dependencies From d46342a18399c46e8cfa32fa9249fd04b46d85ba Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Tue, 13 May 2025 19:25:20 +0300 Subject: [PATCH 09/11] Upgrading Q1 2025 Trial to Q2 2025 Licensed Version --- ...-2025-trial-to-q2-2025-purchase-license.md | 31 +++++++++++++++++++ ...g-up-your-telerik-reporting-license-key.md | 1 + 2 files changed, 32 insertions(+) create mode 100644 knowledge-base/upgrade-q1-2025-trial-to-q2-2025-purchase-license.md diff --git a/knowledge-base/upgrade-q1-2025-trial-to-q2-2025-purchase-license.md b/knowledge-base/upgrade-q1-2025-trial-to-q2-2025-purchase-license.md new file mode 100644 index 000000000..a8c74a196 --- /dev/null +++ b/knowledge-base/upgrade-q1-2025-trial-to-q2-2025-purchase-license.md @@ -0,0 +1,31 @@ +--- +title: Upgrading Q1 2025 Trial to Q2 2025 Licensed Version +description: Learn how a trial user who started their trial a week ago using a Q1 2025 version can update to a Q2 2025 version using NuGet. +type: how-to +page_title: How to Upgrade Q1 2025 Trial to Q2 2025 Licensed Version +slug: upgrade-q1-2025-trial-to-q2-2025-purchase-license +tags: trial, message, license, report, reporting +res_type: kb +--- + +## Environment + +| Version | Product | Author | +| ---- | ---- | ---- | +| Q2 2025| Telerik Reporting |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| + +## Description + +This article aims to explain how a trial user who started their trial less than 30 days before the Q2 2025 release using a **Q1 2025** version can update to a **Q2 2025** commercial version using NuGet. + +## Solution + +For a successful upgrade, these users must consider the change in the NuGet package name — the Q2 2025 package has no trial identifier in the name. These clients must uninstall the Q1 2025 version and install the Q2 2025 version for a successful upgrade. + +>caution Starting with [Telerik Reporting version Q1 2025](https://www.telerik.com/blogs/license-key-files-telerik-kendo-ui-products-2025-update), you must activate the product through a [license key]({%slug setting-up-license-key%}) (trial or commercial). To upgrade from a Trial to a Developer (or commercial) license, purchase a license and then download a new license key, without re-installing the product. + + +## See Also + +* [Setting Up Telerik Reporting License Key]({%slug setting-up-license-key%}) +* [Licensing before 2025]({%slug telerikreporting/licensing%}) diff --git a/licensing/setting-up-your-telerik-reporting-license-key.md b/licensing/setting-up-your-telerik-reporting-license-key.md index 33f65916a..b1c2c33f5 100644 --- a/licensing/setting-up-your-telerik-reporting-license-key.md +++ b/licensing/setting-up-your-telerik-reporting-license-key.md @@ -107,3 +107,4 @@ Whenever you purchase a new Telerik Reporting license or renew an existing one, * [License Activation Errors and Warnings]({%slug license-errors-and-warnings%}) * [Adding the License Key to CI Services]({%slug license-key-ci-services%})) * [Frequently Asked Questions about Your Telerik Reporting License Key]({%slug license-frequently-asked-questions%}) +* [Upgrading Q1 2025 Trial to Q2 2025 Licensed Version]({%slug upgrade-q1-2025-trial-to-q2-2025-purchase-license%}) From d7501e372ce075520a5372e8c19a813a23c52d7b Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Thu, 15 May 2025 11:59:17 +0300 Subject: [PATCH 10/11] Link the 'before' KB --- licensing/setting-up-your-telerik-reporting-license-key.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/licensing/setting-up-your-telerik-reporting-license-key.md b/licensing/setting-up-your-telerik-reporting-license-key.md index b1c2c33f5..53c46cb01 100644 --- a/licensing/setting-up-your-telerik-reporting-license-key.md +++ b/licensing/setting-up-your-telerik-reporting-license-key.md @@ -2,7 +2,7 @@ title: Setting Up Telerik Reporting License Key page_title: "Learn how to set up the Telerik Reporting License Key." slug: license-key -tags: license, key, telerik, reporting +tags: license, key, telerik, reporting, licensing published: True position: 1 --- @@ -108,3 +108,4 @@ Whenever you purchase a new Telerik Reporting license or renew an existing one, * [Adding the License Key to CI Services]({%slug license-key-ci-services%})) * [Frequently Asked Questions about Your Telerik Reporting License Key]({%slug license-frequently-asked-questions%}) * [Upgrading Q1 2025 Trial to Q2 2025 Licensed Version]({%slug upgrade-q1-2025-trial-to-q2-2025-purchase-license%}) +* [Licensing before 2025]({%slug telerikreporting/licensing%}) From 678d92f5cc3f95d41ad29e627ce132042fe7d8a5 Mon Sep 17 00:00:00 2001 From: Yordan Mitev Date: Fri, 16 May 2025 12:03:14 +0300 Subject: [PATCH 11/11] Update errors table and FAQ --- licensing/license-errors-and-warnings.md | 31 +++++------ licensing/license-faq.md | 66 ++++-------------------- 2 files changed, 25 insertions(+), 72 deletions(-) diff --git a/licensing/license-errors-and-warnings.md b/licensing/license-errors-and-warnings.md index 40f2ba3c8..5e9b41fa4 100644 --- a/licensing/license-errors-and-warnings.md +++ b/licensing/license-errors-and-warnings.md @@ -11,10 +11,10 @@ position: 7 Starting with the [2025 Q1 (19.0.25.211)](https://www.telerik.com/support/whats-new/reporting/release-history/progress-telerik-reporting-2025-q1-19-0-25-211) release, using Telerik Reporting without a license or with an invalid license causes specific license warnings and errors. This article defines what an invalid license is, explains what is causing it, and describes the related license warnings and errors. -A missing, expired, or invalid license will result in: +If a valid license cannot be found: - - A watermark appears on each report document page. - - A warning message appearing in the build log: +- A watermark appears on each document page in the report. +- A [warning message](#license-errors-and-warnings) appears in the build log: ```` Telerik and Kendo UI Licensing warning TKL002: No Telerik and Kendo UI License file found. @@ -44,7 +44,6 @@ Telerik and Kendo UI Licensing warning TKL002: No Telerik and Kendo UI License f Telerik and Kendo UI Licensing warning TKL004: Unable to locate licenses for all products. ```` - ## Invalid License An invalid license can be caused by any of the following: @@ -60,22 +59,20 @@ An invalid license can be caused by any of the following: Using the Telerik Reporting in a project with an expired or missing license, the `Telerik.Licensing` build task will indicate the following errors or conditions: -|**Condition or Error**|**Message Code**|**Solution**| +|Condition or Error|Message Code|Solution| |----|----|----| -|`No license key is detected`|TKL002|[Install a license key]({%slug license-key%}) to activate Telerik Reporting and remove the error message.| -|`Invalid license key`|TKL003|[Download a new license key]({%slug license-key%}#downloading-the-license-key) and install it to activate Telerik Reporting and remove the error message.| -|`Your subscription license has expired.`|TKL103; TKL104|Renew your subscription and [download a new license key]({%slug license-key%}#downloading-the-license-key).| -|`Your perpetual license is invalid.`|TKL102||You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following:
  • Renew your subscription and [download a new license key]({%slug license-key%}#downloading-the-license-key)
  • Downgrade to a Telerik Reporting version included in your perpetual license, as indicated in the message.
| -|`Your trial license has expired.`|TKL105|Purchase a commercial license to continue using the product.| -|`Your license is not valid for the detected product(s).`|TKL101|Review the purchase options for the listed products.
Alternatively, remove the references to the listed packages from `package.json`.| -|`Unable to locate licenses for all products`|TKL004|Your license is not valid for all Telerik and Kendo products added to your project. If you have already purchased the required license, then update your license key]({%slug license-key%}).| -|`No Telerik or Kendo UI product references detected in project`|TKL001|
  • If you use Telerik products and see this message, update the Telerik.Licensing package to version 1.4.9 or later.
  • If you do not use Telerik products, remove the Telerik.Licensing NuGet reference from your project.
| - -Starting with the 2025 Q2 release of Telerik Reporting, all conditions above will be treated as errors. +|`No Telerik and Kendo UI License file found`|TKL002|[Set up a license key]({%slug license-key%}) to activate Telerik Reporting and remove the error message.| +|`Corrupted Telerik and Kendo UI License Key content`|TKL003|[Download a new license key]({%slug license-key%}#downloading-the-license-key) and use it to activate Telerik Reporting and remove the error message.| +| `Unable to locate licenses for all products` | TKL004 | Your license is not valid for all Telerik and Kendo products added to your project. If you have already purchased the required license, then [update your license key]({%slug license-key%}). | +|`Your subscription has expired`|TKL103; TKL104|Renew your subscription and [download a new license key]({%slug license-key%}#downloading-the-license-key).| +|`Your current license has expired`|TKL102|You are using a product version released outside the validity period of your perpetual license. To remove the error message, do either of the following:
  • Renew your subscription and [download a new license key]({%slug license-key%}#downloading-the-license-key)
  • Downgrade to a Telerik Reporting version covered by your perpetual license, as specified in the message.
| +|`Your trial expired`|TKL105|Purchase a commercial license to continue using the product.| +|`Telerik Reporting is not listed in your current license file`|TKL101|Review the purchase options for the listed products.| +| `No Telerik or Kendo UI product references detected in project.` | TKL001 | If you use Telerik products and see this message, update the `Telerik.Licensing` package to version `1.4.9` or later. If you do not use Telerik products, remove the `Telerik.Licensing` NuGet reference from your project | # See Also -* [Setting Up Your License Key]({%slug license-key%})) +* [Setting Up Your License Key]({%slug license-key%}) * [Frequently Asked Questions about Your Telerik Reporting License Key]({%slug license-frequently-asked-questions%}) -* [Adding the License Key to CI Services]({%slug license-key-ci-services%})) +* [Adding the License Key to CI Services]({%slug license-key-ci-services%}) * [License Agreement](https://www.telerik.com/purchase/license-agreement/reporting-dlw-s) diff --git a/licensing/license-faq.md b/licensing/license-faq.md index 1a9a5fbf0..eaad032ae 100644 --- a/licensing/license-faq.md +++ b/licensing/license-faq.md @@ -24,60 +24,16 @@ You will need to obtain and install a new license key after starting a trial, re ## Will the product function with an expired license key? -This depends on your license type. - -* __Perpetual licenses__ will continue to function normally with an expired license key. - - However, the following will happen if you update or install a package version that is released after the expiration date of the license: - - - A watermark appears on each report document page - - A warning message similar to the one shown below is logged in the build log - -* __Subscription licenses__ used in deployed applications will continue to function normally. - - However, the following will happen if you rebuild the application with an expired subscription license: - - - A watermark appears on each report document page - - A warning message similar to the one shown below is logged in the build log - -* __Trial licenses__ will prevent the applications from functioning normally once the trial period has expired. - - The following will happen if you try to build or run the application: - - - A watermark appears on each report document page. - - A warning message similar to the following one is logged in the build log: - -```` -Telerik and Kendo UI Licensing warning TKL002: No Telerik and Kendo UI License file found. -Telerik and Kendo UI Licensing warning TKL002: The following locations were searched: -Telerik and Kendo UI Licensing warning TKL002: * TELERIK_LICENSE (EnvironmentVariable) -Telerik and Kendo UI Licensing warning TKL002: * KENDO_UI_LICENSE (EnvironmentVariable) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\CSharp\.NET 6\WinFormsIntegrationDemo\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\CSharp\.NET 6\WinFormsIntegrationDemo\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\CSharp\.NET 6\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\CSharp\.NET 6\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\CSharp\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\CSharp\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\Examples\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\Telerik Reporting 2025 Q1\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\Progress\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Program Files (x86)\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\telerik-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\kendo-ui-license.txt (RecursiveFilePath) -Telerik and Kendo UI Licensing warning TKL002: * C:\Users\user1\AppData\Roaming\Telerik\telerik-license.txt (UserDirectory) -Telerik and Kendo UI Licensing warning TKL002: * C:\Users\user1\AppData\Roaming\Telerik\kendo-ui-license.txt (UserDirectory) -Telerik and Kendo UI Licensing warning TKL002: Activate a License Key file at https://prgress.co/3PBSVoC -Telerik and Kendo UI Licensing warning TKL101: Telerik Reporting is not listed in your current license file. -Telerik and Kendo UI Licensing warning TKL004: Unable to locate licenses for all products. -```` - -See the [Invalid License]({%slug license-errors-and-warnings%}#invalid-license) section for more information. - -Note that future updates of Telerik Reporting may restrict or disable some features when no valid license is present. +This depends on the Telerik Reporting [license type (perpetual, subscription, or trial)](https://www.telerik.com/purchase/faq/licensing-purchasing#licensing): + +* *Perpetual licenses* function normally with an expired license key, as long as the application is using a Telerik Reporting version that was released before the expiration date of the license. +* *Subscription licenses* function normally in already deployed applications, but you cannot rebuild and republish the app. +* *Trial licenses* function normally only within the 30-day trial period. + +If none of the above conditions are met, the following behaviors occur: + +* A watermark appears on each report document page. +* A [warning message]({%slug license-errors-and-warnings%}) appears in the application's build log. ## I updated the version of the Telerik Reporting packages in my project and the invalid license errors have appeared. What is the cause of this behavior? @@ -117,7 +73,7 @@ To enforce the use of the license key file, unset the environment variable. ## Are earlier versions of Telerik Reporting affected? -No, versions released prior to __January 2025__ do not require a license key. +No, versions released prior to January 2025 do not require a license key. ## What happens if I make a change to non-Telerik parts of the code after the subscription expires?