chore: update docs to reflect new package distribution

radkostanev · radkostanev · commit bc4c365617bd · 2025-05-14T15:23:03.000+03:00
diff --git a/_contentTemplates/common/get-started.md b/_contentTemplates/common/get-started.md
@@ -13,9 +13,9 @@
 
 ## Step 0: Download Telerik UI for Blazor
 
-* If you have already purchased a Telerik UI for Blazor license, continue with the [next step and install a license key](#step-1-install-a-license-key).
+* If you have already purchased a Telerik UI for Blazor commercial license, continue with the [next step and install a license key](#step-1-install-a-license-key).
 
-* If you are new to UI for Blazor and haven't purchased a license yet, you must <a href="https://www.telerik.com/download-trial-file/v2-b/ui-for-blazor" target="_blank">download and install the trial version</a> of the UI for Blazor components&mdash;this will activate your free trial and allow you to use the components. During the installation, select the **Set up Telerik NuGet package source** checkbox and the installer will configure the Telerik [online NuGet feed](slug:installation/nuget) automatically. You will use this feed later in the tutorial. 
+* If you are new to UI for Blazor and haven't purchased a license yet, you can <a href="https://www.telerik.com/try/ui-for-blazor" target="_blank">Start a Free Trial</a> by downloading and installing the UI for Blazor components&mdash;this will activate your free trial and allow you to use the components. During the installation, select the **Set up Telerik NuGet package source** checkbox and the installer will configure the Telerik [online NuGet feed](slug:installation/nuget) automatically. You will use this feed later in the tutorial. 
 
 >Trial users must complete the installation of the components. Otherwise their trial license will not activate and you cannot complete the tutorial successfully.
 
@@ -127,7 +127,7 @@ To setup a local NuGet package source, so you can install the Telerik components
 #navigate-account
 1. Go to [Downloads](https://www.telerik.com/account/downloads) in your [Telerik account](https://www.telerik.com/account/).
 
-1. On the loaded page choose from your purchased products or trial downloads **Progress® Telerik® UI for Blazor**, and click on it.
+1. On the loaded page click on **Progress® Telerik® UI for Blazor**.
 #end
 
 
diff --git a/_contentTemplates/common/js-interop-file.md b/_contentTemplates/common/js-interop-file.md
@@ -24,10 +24,6 @@
 <head>
     . . .
     <script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js"></script>
-
-    <!-- For Trial licenses, use
-      <script src="_content/Telerik.UI.for.Blazor.Trial/js/telerik-blazor.js"></script>
-    -->
 </head>
 ````
 #end
@@ -37,10 +33,6 @@
 <head>
     . . .
     <link rel="stylesheet" href="_content/Telerik.UI.for.Blazor/css/kendo-theme-default/all.css" />
-
-    <!-- For Trial licenses, use
-        <link rel="stylesheet" href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-theme-default/all.css" />
-      -->
 </head>
 ````
 #end
diff --git a/common-features/icons.md b/common-features/icons.md
@@ -89,8 +89,6 @@ In version 4.6.0 of Telerik UI for Blazor, the font icon styles were separated i
 ````RAZOR
 <!-- If using static assets from the NuGet package -->
 <link href="_content/Telerik.UI.for.Blazor/css/kendo-font-icons/font-icons.css" rel="stylesheet" />
-<!-- If using static assets from a Trial NuGet package -->
-<link href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-font-icons/font-icons.css" rel="stylesheet" />
 
 <!-- If using the Telerik Blazor CDN - set the correct version number in the URL -->
 <link href="https://blazor.cdn.telerik.com/blazor/{{site.uiForBlazorLatestVersion}}/kendo-font-icons/font-icons.css" rel="stylesheet" type="text/css" />
diff --git a/deployment/troubleshooting.md b/deployment/troubleshooting.md
@@ -77,7 +77,10 @@ namespace MyBlazorAppName
 * We have had reports that indicate missing project references do not copy the static assets. For example, in an ASP.NET Core hosted WebAssembly project the server project usually has a project reference to the Blazor project. If that reference is missing, the static assets might not be present in the output.
 
 
-### Trial Message
+### Your Deployed Application Shows a Banner or a Watermark
+
+Ensure that you have set up an environment variable by following the steps from the [Use License Keys in CI/CD](slug:installation-license-key) article.
+
 
 `Trial Message` - if the machine that performs the build has access to a trial version of our NuGet package, the framework may get confused and copy a trial assembly to the publish location and you may see the trial messages live. Solutions are available in the [Upgrade Troubleshooting - I Still See the Trial Message](slug:upgrade-tutorial#i-still-see-the-trial-watermark-and-banner) article.
 
diff --git a/getting-started/client-blazor.md b/getting-started/client-blazor.md
@@ -52,7 +52,7 @@ This article explains how to get the <a href = "https://www.telerik.com/blazor-u
 2. Install the Telerik Blazor NuGet package:
 
    1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate with your [Telerik account](https://www.telerik.com/account/) user name and password.
-   1. Select the **Browse** tab, find the NuGet package, and click **Install**. Commercial license holders should install `Telerik.UI.for.Blazor`. Trial users should install `Telerik.UI.for.Blazor.Trial`.
+   1. Select the **Browse** tab, find the `Telerik.UI.for.Blazor` NuGet package, and click **Install**.
 
    ![Add Telerik Blazor Package to Client Project](images/add-telerik-nuget-to-client-app.png)
 
diff --git a/getting-started/server-blazor.md b/getting-started/server-blazor.md
@@ -52,7 +52,7 @@ Blazor Server runs C# on the server and updates the UI in the browser through a
 2. Install the Telerik Blazor NuGet package:
 
    1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate with your [Telerik account](https://www.telerik.com/account/) user name and password.
-   1. Select the **Browse** tab, find the NuGet package, and click **Install**. Commercial license holders should install `Telerik.UI.for.Blazor`. Trial users should install `Telerik.UI.for.Blazor.Trial`.
+   1. Select the **Browse** tab, find the `Telerik.UI.for.Blazor` NuGet package, and click **Install**.
 
 ![Add Telerik Blazor Package to the project](images/add-telerik-nuget-to-server-app.png)
 
diff --git a/getting-started/vs-code-integration/document-processing-wizard.md b/getting-started/vs-code-integration/document-processing-wizard.md
@@ -41,7 +41,6 @@ Upon successful completion of the above steps, the wizard must appear like this:
 The Telerik Document Processing Configuration wizard allows you to:
 
 * Select which libraries to use.
-* Use the commercial or trial versions of the libraries.
 * Select the project (`.csproj` file), in which you want to install the libraries. This option is useful when the user has many open projects in the workspace. If a library has any dependencies, they are automatically checked.
 
 The table below lists the assemblies that will be selected for each library:
diff --git a/getting-started/vs-code-integration/new-project-wizard.md b/getting-started/vs-code-integration/new-project-wizard.md
@@ -58,27 +58,23 @@ Here you can select the desired hosting model&mdash;[**WebApp**](slug:getting-st
 
 The available target framework options are updated upon selecting the hosting model.
 
-#### Section 6: Select Your License Type
-
-Select your license type - **Commercial** (**Paid**) or **Trial**.
-
-#### Section 7: Choose How to Distribute the Client Assets
+#### Section 6: Choose How to Distribute the Client Assets
 
 Choose whether to load the required Telerik UI stylesheet and JS Interop file as [static NuGet assets](slug:getting-started/what-you-need#css-theme-and-javascript-files) or load them from the [Telerik CDN](slug:common-features-cdn).
 
-#### Section 8: Enable or Disable Localization
+#### Section 7: Enable or Disable Localization
 
 Choose whether to use [localization](slug:globalization-localization) in the project or not.
 
-#### Section 9: Select the Preferred Icon Type
+#### Section 8: Select the Preferred Icon Type
 
 Decide if you want to switch to using [Font Icons](slug:common-features-icons) instead of the default SVG icons.
 
-#### Section 10: Select Target Framework
+#### Section 9: Select Target Framework
 
 The available .NET framework versions vary depending on the selected hosting model.
 
-#### Section 11: Select Theme
+#### Section 10: Select Theme
 
 Select your desired [theme](slug:themes-overview) for your project. Click **See All Swatches** to explore the available [theme color variations](slug:themes-overview#basics).
 
diff --git a/getting-started/vs-integration/convert-project-wizard.md b/getting-started/vs-integration/convert-project-wizard.md
@@ -109,10 +109,7 @@ The issue can manifest in a couple of ways:
 * The components have no styling.
 * There are JavaScript errors that Telerik objects cannot be found.
 
-The most common reason for this problem is a mismatch between the installed version and the actual license that you have. For example:
-
-* Only a trial version is installed on your development machine, but you already have a commercial license, yet you never installed the commercial version.
-* The wizard did not properly detect the installed version.
+The most common reason for this problem is a mismatch between the installed version and the actual license that you have.
 
 The cause are wrong paths to the needed web assets. To resolve this open the index file:
 
diff --git a/getting-started/vs-integration/options.md b/getting-started/vs-integration/options.md
@@ -50,8 +50,6 @@ C:\Users\[username]\AppData\Roaming\Telerik\Updates
 
 * **Suggest project upgrades for Telerik product versions available on my computer**—`True` by default.
 
-* **Suggest upgrades when an equal Dev release is detected on projects using a Trial**—`True` by default.
-
 ## See Also
 
 * [Creating New Projects with Visual Studio](slug:getting-started-vs-integration-new-project )
diff --git a/getting-started/vs-integration/upgrade-wizard.md b/getting-started/vs-integration/upgrade-wizard.md
@@ -24,7 +24,6 @@ The Telerik Blazor Upgrade Wizard will do the following:
 
 * Update the version of the referenced Blazor NuGet package. It will also update the package source in the solution-based NuGet config file.
 * Update the version of the theme reference, but only when using CDN. Otherwise, [update the theme manually](slug:getting-started-vs-integration-new-project#step-3-select-theme).
-* Update all local script and style and NuGet package references if you upgrade from a Trial to a Dev version.
 * It will add the new keys in the default (English) localization file.
 
 ## Projects for Upgrade
diff --git a/getting-started/web-app.md b/getting-started/web-app.md
@@ -62,7 +62,7 @@ This article explains how to use the Telerik UI for Blazor components in a Blazo
 1. Install the Telerik Blazor NuGet package:
 
    1. Select the `telerik.com` **Package source** that you [added earlier](#step-3-add-the-telerik-nuget-feed-to-visual-studio). As this is a private NuGet feed, you must authenticate with your [Telerik account](https://www.telerik.com/account/) username and password.
-   1. Select the **Browse** tab, find the NuGet package, and click **Install**. Commercial license holders must install `Telerik.UI.for.Blazor`. Trial users must install `Telerik.UI.for.Blazor.Trial`.
+   1. Select the **Browse** tab, find the `Telerik.UI.for.Blazor` NuGet package, and click **Install**.
 
 ## Step 5: Enable the Blazor UI Components
 
diff --git a/getting-started/what-you-need.md b/getting-started/what-you-need.md
@@ -61,8 +61,6 @@ Telerik UI for Blazor is distributed through several private and public NuGet pa
 | `Telerik.Pivot.Core` | Contains base code for the [PivotGrid component](slug:pivotgrid-overview). This NuGet package must not be used separately without the Telerik PivotGrid component. |
 | `Telerik.Pivot.DataProviders.Xmla` | Adds support for [data binding the PivotGrid component to XMLA](slug:pivotgrid-data-binding). This NuGet package must not be used separately without the Telerik PivotGrid component. |
 
->note If you use a trial license, the private package names have a `.Trial` suffix, for example, `Telerik.UI.for.Blazor.Trial`.
-
 ### Getting the Telerik NuGet Packages
 
 To get the public Telerik icon and licensing packages, you only need the default NuGet package source `nuget.org`. To [use a local NuGet feed](https://learn.microsoft.com/en-us/nuget/hosting-packages/local-feeds), download the packages from:
@@ -170,13 +168,9 @@ Register the [Telerik font icon stylesheet](slug:common-features-icons#font-icon
 ````HTML
 <head>
     <link rel="stylesheet" href="_content/Telerik.UI.for.Blazor/css/kendo-theme-default/all.css" />
-    <!-- When using a Trial license -->
-    <!--<link rel="stylesheet" href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-theme-default/all.css" />-->
 
     <!-- Add only if using font icons -->
     <!--<link href="_content/Telerik.UI.for.Blazor/css/kendo-font-icons/font-icons.css" rel="stylesheet" />-->
-    <!-- When using a Trial license -->
-    <!--<link href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-font-icons/font-icons.css" rel="stylesheet" />-->
 
     <!-- main application stylesheet -->
     <link rel="stylesheet" href="css/app.css" />
@@ -204,8 +198,6 @@ The recommended way to register the Telerik Blazor JS file for better loading pe
 <html>
 <head>
    <script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js" defer></script>
-   <!-- When using a Trial license -->
-   <!--<script src="_content/Telerik.UI.for.Blazor.Trial/js/telerik-blazor.js" defer></script>-->
 </head>
 <body>
    <script src="_framework/blazor.web.js" autostart="false"></script>
diff --git a/introduction.md b/introduction.md
@@ -212,9 +212,9 @@ Use [our feedback portal](https://feedback.telerik.com/blazor) to tell us which
 
 Page Templates offer ready-to-use Blazor layouts that effectively integrate the Telerik UI for Blazor components. These templates consist of Building Blocks, which are the individual elements that form the complete layouts. The templates and blocks streamline the development process by providing pre-designed, customizable elements. For more details, refer to the [Building Blocks and Page Templates documentation](https://www.telerik.com/design-system/docs/ui-templates/overview/).
 
-## Trial Version and Commercial License
+## Trial and Commercial License
 
-UI for Blazor is a commercial UI library. You are welcome to explore its full functionality and get technical support from the team when you register for a free 30-day trial. While using the trial package, a watermark and banner will appear over the rendered components.
+UI for Blazor is distributed as a single package, with functionality determined by the applied license. By default, you can register for a free 30-day trial to explore the full capabilities of the library and receive technical support. During the trial period, a visual watermark and banner will appear over rendered components.
 
 To use UI for Blazor commercially, you need to <a href="https://www.telerik.com/purchase/blazor-ui" target="_blank">purchase a license</a>. Feel free to review the Telerik UI for Blazor <a href="https://www.telerik.com/purchase/license-agreement/blazor-ui" target="_blank">License Agreement</a> and get acquainted with the full terms of use.
 
diff --git a/knowledge-base/font-icons-not-rendering.md b/knowledge-base/font-icons-not-rendering.md
@@ -47,9 +47,5 @@ To keep using Font icons in your application use one of the two approaches:
 * Download the [Telerik UI for Blazor package](slug:installation-msi#how-to-download-the-automated-installer) and reference the static assets for the Font Icons in the `_Host.cshtml` or `index.html` (based on the hosting model) file in your application:
 
 ````RAZOR
-<!-- For Trial licenses, use
-<link href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-font-icons/font-icons.css" rel="stylesheet" />
--->
-
 <link href="_content/Telerik.UI.for.Blazor/css/kendo-font-icons/font-icons.css" rel="stylesheet" />
 ````
diff --git a/knowledge-base/jquery-kendo-in-blazor.md b/knowledge-base/jquery-kendo-in-blazor.md
@@ -42,6 +42,4 @@ Should you decide to use jQuery widgets from the Kendo UI suite, here are the th
 
 >tip A sample project that showcases these is available here: [jQuery Kendo Widgets in Blazor](https://github.com/telerik/blazor-ui/tree/master/common/kendo-in-blazor).
 
-The project references a commercial version of UI for Blazor. If you only have a trial license, replace the reference to the NuGet package and to the JS Interop file [accordingly](slug:getting-started/what-you-need).
-
 >note Such an integration is not supported by Telerik.
diff --git a/styling-and-themes/overview.md b/styling-and-themes/overview.md
@@ -100,10 +100,6 @@ The `Telerik.UI.for.Blazor` NuGet package includes only the *Main* swatch of eac
 </head>
 ````
 
-> Trial users must add `.Trial` to the theme URL:
->
-> `<link rel="stylesheet" href="_content/Telerik.UI.for.Blazor.Trial/css/kendo-theme-default/all.css" />`
-
 ## Compatibility and Maintenance
 
 The Telerik themes are decoupled from the Telerik Blazor components, which leads to the following usage requirements:
diff --git a/troubleshooting/js-errors.md b/troubleshooting/js-errors.md
@@ -45,8 +45,6 @@ You can check if this is the case by inspecting the Network tab of your browser
     * Discuss the case with your network administrators to have our CDN allowed.
     * Use [static assets](slug:getting-started/what-you-need#css-theme-and-javascript-files) from the app folder to avoid going to the cloud.
 
-* The application was upgraded from a trial to a commercial license, but the path to the file was not. See the [Upgrade from Trial to Commercial](slug:upgrade-tutorial#upgrade-from-trial-to-commercial) section for details.
-
 * Static assets are not enabled on the server project, or the hosting environment does not work well with them. You need to ensure that the static assets are available after the build and on the deployment server - they are in the local NuGet cache, under a path similar to `C:\Users\<theUser>\.nuget\packages\telerik.ui.for.blazor\<theVersion>\staticwebassets`. It is also possible that the hosting server does not support static assets or has issues with them and you may need to confirm this with the hosting provider or by testing with a simple package having a static asset to see whether it gets returned.
     * [Clearing the NuGet cache](https://docs.microsoft.com/en-us/nuget/consume-packages/managing-the-global-packages-and-cache-folders#clearing-local-folders), then running a `Clean` and `Rebuild` on the solution may fix the problem in case something went wrong with fetching the NuGet package. In case `Clean` does not clean up the `bin` and `obj` folders, you can also delete them manually before `Rebuild`.
 
diff --git a/troubleshooting/nuget-feed.md b/troubleshooting/nuget-feed.md
@@ -30,7 +30,6 @@ Regardless of the cause for the issue, it is recommended that you start from the
 The most common reasons for issues with the private Telerik NuGet feed are related to:
 
 * Authentication and credentials.
-* Licensing. For example, requesting commercial packages with a trial license or vice-versa.
 * Missing or wrong local configuration (`NuGet.Config`).
 * Network connectivity issues, including **proxies** and **firewalls**.
 
@@ -40,8 +39,6 @@ Errors like `Unable to load the service index for source https://nuget.telerik.c
 
 To verify if you can access the Telerik NuGet server and the expected packages, open https://nuget.telerik.com/v3/search?q=blazor&prerelease=true&skip=0&take=100&semVerLevel=2.0.0 directly in the web browser and enter your Telerik credentials in the prompt.
 
-As a result, you will see a JSON output with the NuGet packages and versions that are available for you. Depending on your license, search for `Telerik.UI.for.Blazor` or `Telerik.UI.for.Blazor.Trial`.
-
 If the above URL doesn't open, you have either come across a local networking issue or [the NuGet server is down](#error-503-service-unavailable).
 
 If you can access the feed in the browser, but you do not see the packages in Visual Studio, most likely the problem is caused by entering wrong credentials or using a different Telerik account. Make sure your saved credentials are correct. Also, you must not have a `NuGet.Config` file in your project as it may bring in invalid credentials and project-level configuration files override the global ones.
diff --git a/upgrade/overview.md b/upgrade/overview.md
