Skip to content

Commit 7ec15ff

Browse files
committed
license variables
1 parent f643f13 commit 7ec15ff

File tree

5 files changed

+19
-5
lines changed

5 files changed

+19
-5
lines changed

distribution-and-licensing/license-key.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,4 +196,5 @@ Starting with the 2025 Q2 release of the product in May 2025, all conditions abo
196196
* [License Agreement]({%slug license-agreement%})
197197
* [Redistributing Telerik Document Processing]({%slug installation-deploying-telerik-document-processing%})
198198
* [Unable to find package Telerik.Licensing]({%slug dpl-package-update-failure-license%})
199+
* [Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release]({%slug handling-license-file-name-changes%})
199200

knowledge-base/handling-license-file-name-changes.md

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,26 @@ res_type: kb
1616

1717
## Description
1818

19-
After downloading the License Key file by using the VS2022 extensions menu, when I build a simple console app with the DPLs, I get the following error:
20-
19+
After downloading the License Key file by using the VS2022 extensions menu:
20+
![Download License key](images/download-license-key.png)
21+
22+
when building a simple console app with the Telerik Document Processing libraries, you get the following error:
23+
24+
![License error](images/license-error.png)
2125

2226
## Solution
2327

2428
It may be caused by an old KENDO_UI_LICENSE environment variable. So, delete it and invoke `refreshenv` command. If the rebuild has the same error again:
25-
1. Go to telerik.com and generate a new license file.
26-
2. Compare the license key with the one downloaded from the extensions. If it indeed looks different than the one VS2022 got, replace the original telerik-license.txt file with the newly downloaded one.
27-
3.Next, I restart VS2022 (to ensure it has a fresh copy env vars) and compile the project. It is expected to work:
2829

30+
1\. Go to telerik.com and generate a new [License Key](https://www.telerik.com/account/your-licenses/license-keys).
31+
32+
2\. Compare the license key with the one downloaded from the extensions. If it indeed looks different than the one VS2022 got, replace the original telerik-license.txt file with the newly downloaded one.
33+
34+
3\.Next, I restart VS2022 (to ensure it has a fresh copy env vars) and compile the project. It is expected to work:
35+
36+
37+
![License Fixed](images/license-fixed.png)
38+
39+
## See Also
40+
41+
* [Unable to find package Telerik.Licensing]({%slug dpl-package-update-failure-license%})
20.2 KB
Loading
17.2 KB
Loading
28.6 KB
Loading

0 commit comments

Comments
 (0)