diff --git a/getting-started/activating-your-license/licensing-faq.md b/getting-started/activating-your-license/licensing-faq.md index d5401e3904..a9b5677b52 100644 --- a/getting-started/activating-your-license/licensing-faq.md +++ b/getting-started/activating-your-license/licensing-faq.md @@ -15,7 +15,7 @@ This article lists the answers to the most frequently asked questions (FAQs) abo Yes, the license key expires at the end of your subscription: * For trial users, this is at the end of your 30-day trial period. -* For commercial license holders, this is when your subscription term expires. +* For commercial license holders (as of 2025 Q2), this is when your subscription term expires. You need to download and install a new license key after: diff --git a/getting-started/activating-your-license/setting-up-your-license.md b/getting-started/activating-your-license/setting-up-your-license.md index 0ac26b32f1..b12b947754 100644 --- a/getting-started/activating-your-license/setting-up-your-license.md +++ b/getting-started/activating-your-license/setting-up-your-license.md @@ -9,7 +9,7 @@ position: 0 # Setting Up Your License Key File -Telerik UI for ASP.NET AJAX requires activation through a license key for both trial and commercial licenses. This article describes how to download your personal license key and use it to activate the UI for ASP.NET AJAX components. +Telerik UI for ASP.NET AJAX requires activation through a license key for trial licenses. This article describes how to download your personal license key and use it to activate the UI for ASP.NET AJAX components. >note Starting with Telerik UI for ASP.NET AJAX 2025 Q1 release, you must activate the UI components by providing a license key file. Previous versions do not require a license key. @@ -28,6 +28,10 @@ Follow the steps below for [manual](#manual-installation) license key installati An [invalid or missing license key results in app build warnings]({%slug getting-started/activating-your-license/license-key-errors%}) and watermarks in the application UI. +A missing license file causes a banner and a watermark to appear: + +![Grid with watermarks](../images/watermark.png "Grid with watermarks") + >warning The license key file is personal and confidential. Do not commit this file to source control and do not save it to a publicly accessible location! ## Manual Installation diff --git a/getting-started/images/watermark.png b/getting-started/images/watermark.png new file mode 100644 index 0000000000..f566217fcb Binary files /dev/null and b/getting-started/images/watermark.png differ diff --git a/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md b/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md index 79d5dfd45a..188f3a4036 100644 --- a/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md +++ b/upgrade-compatibility/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version.md @@ -13,6 +13,9 @@ position: 0 This article explains how to upgrade the version of the TelerikĀ® UI for ASP.NET AJAX controls and how to switch from a Trial to a Developer license. +>warning Starting with the 2025 Q1 release, the trial Telerik AJAX components require activation with a license key to function without interruption. For more information regarding the licensing review the +> [Setting Up Your License Key File]({%slug getting-started/activating-your-license/setting-up-your-license%}) and [FAQ]({%slug getting-started/activating-your-license/licensing-faq%}). + ## Upgrade to a Newer Version of TelerikĀ® UI for ASP.NET AJAX To upgrade the Telerik controls in your project: @@ -41,6 +44,8 @@ The automatic upgrade is possible if you use the UI for ASP.NET AJAX Visual Stud >tip The Upgrade Wizard does not modify the `` sections in the web.config file or the entries in the `licenses.licx` file. If you encounter errors such as "Could not load file or assembly 'Telerik.Web.UI'" after an upgrade, check that the web.config includes binding redirects for old assembly versions. Additionally, ensure the `licenses.licx` file does not contain outdated entries; deleting the file contents, saving it and rebuilding the solution can regenerate it with the correct references. +>warning As of 2025 Q1 the `licenses.licx` file is removed and replaced with the new licensing mechanism. + ### Manual Upgrade The manual upgrade gives you the freedom to control each step of the process. In short, you just need to replace the assembly references with the new ones.