You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: knowledge-base/license-not-recognized-telerik-document-processing-libraries.md
+8-18Lines changed: 8 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -18,11 +18,11 @@ ticketid: 1690929
18
18
19
19
## Description
20
20
21
-
This article aims to address potential licensing issues while generating Excel files with Telerik Document Processing Libraries during runtime testing. The generated file contains a "License" tab with a trial message, despite the Build Output window indicating a valid license. The issue arises in a multi-project (e.g. Blazor WASM) application setup, where dependencies are shared across projects.
21
+
This article aims to address potential licensing issues while generating Excel (or PDF, DOCX, etc.) files with Telerik Document Processing Libraries during **runtime** testing. The generated file contains a "License" sheet (or a watermark) with a trial message, despite the **Build Output** window indicating a valid license. The issue arises in a multi-project (e.g. Blazor WASM) application setup, where dependencies are shared across projects.
22
22
23
23
## Cause
24
24
25
-
This issue generally occurs due to incomplete license validation during runtime in complex setups, particularly when using shared libraries or plugin architectures. Even if the license is validated during build, runtime environments may fail to recognize it due to transitive dependency limitations.
25
+
This issue generally occurs due to incomplete license validation during runtime in complex setups, particularly when using shared libraries or plugin architectures. *Even if the license is validated during build time, runtime environments may fail to recognize it due to transitive dependency limitations.*
26
26
27
27
## Solution
28
28
@@ -32,17 +32,7 @@ To ensure proper license validation and eliminate trial messages, follow the ste
32
32
33
33
2.**Explicit License Registration**: Add a call to `TelerikLicensing.Register()` early in your application lifecycle. For Blazor WASM applications, include this call in the `Program.cs` file. This approach validates the license explicitly.
3.**Verify Assemblies**: Ensure no trial versions of Telerik assemblies are referenced in any project. Replace trial assemblies with licensed versions, if necessary.
35
+
3.**Verify Assemblies**: Ensure **no trial** versions of Telerik assemblies are referenced in any project. Replace [trial assemblies]({%slug upgrade-trial-to-licensed-version%}) with licensed ones, if such even exist.
46
36
47
37
4.**Enable Diagnostics**: Add the following property to your `.csproj` file to enable detailed licensing diagnostics during build and runtime:
48
38
```xml
@@ -52,15 +42,15 @@ To ensure proper license validation and eliminate trial messages, follow the ste
52
42
```
53
43
Review the diagnostic output for clues about license validation issues.
54
44
55
-
5.**Direct Package References**: Add references to Telerik Document Processing Libraries and Telerik UI for Blazor NuGet packages directly in the Blazor WASM project. This resolves transitive dependency limitations.
45
+
5.**Direct Package References**: Add references to the Telerik Document Processing Libraries NuGet packages directly in the Blazor WASM project. This resolves transitive dependency limitations.
56
46
57
47
6.**Avoid Environment Variables**: Use only the `telerik-license.txt` file for license delivery instead of environment variables, which can cause issues due to length limitations.
58
48
59
49
By following these steps, runtime validation issues should resolve, and the trial message will no longer appear in generated documents.
0 commit comments