Skip to content

Commit 3e007a3

Browse files
dimodintacheva
authored and
ntacheva
committed
docs(Common): Add troubleshooting info for license verification banner
1 parent 1605dda commit 3e007a3

File tree

2 files changed

+29
-0
lines changed

2 files changed

+29
-0
lines changed

installation/license-key.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,28 @@ The new license key includes information about all previous purchases. This proc
6161
* If you used the [manual license key installation](#manual-installation), then repeat the same steps.
6262
* To [update your license key in CI/CD environments](slug:deployment-license-key), get your new license key and update the environment variable value.
6363

64+
## Using Telerik Packages in Referenced Projects
65+
66+
Telerik UI for Blazor may be used in a referenced project in a multi-project app. For example, in the **Client** project of a WebAssembly app that uses server-side pre-rendering. In such cases, you can briefly see a yellow banner in the browser, which says "We couldn't verify your license key for Telerik UI for Blazor. Please see the build log for details and resolution steps".
67+
68+
There are two alternative ways to avoid the warning banner:
69+
70+
* Set `PrivateAssets="none"` to the Telerik UI for Blazor NuGet package registration tag.
71+
````XML.skip-repl
72+
<PackageReference Include="Telerik.UI.for.Blazor" Version="{{site.uiForBlazorLatestVersion}}" PrivateAssets="none" />
73+
````
74+
75+
* Reference the `Telerik.Licensing` package explicitly in all projects that reference other projects with Telerik packages. You can use the same version that is referenced by the `Telerik.UI.for.Blazor` NuGet package, or a newer version.
76+
````XML.skip-repl
77+
<ItemGroup>
78+
<PackageReference Include="Telerik.Licensing" Version="*" />
79+
</ItemGroup>
80+
````
81+
82+
## Troubleshooting
83+
84+
Refer to the [Troubleshooting License Key Errors](slug:troubleshooting-license-key-errors) page to find out what license key warnings you may see during application build and what they mean.
85+
6486
## Frequently Asked Questions
6587

6688
### Does the license key expire?

troubleshooting/license-key-errors.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ A Telerik license key error may occur in the following scenarios:
2222
* The license key is outdated or does not include the product version that you are using.
2323
* Your subscription license or trial has expired.
2424
* You have different conflicting license keys in the same environment. For example, using one global license key and one in the app. Or, using a license key file together with an environment variable in CI/CD environment.
25+
* Telerik UI for Blazor is used in the **Client** project of a WebAssembly app that uses pre-rendering. In such cases, you can briefly see a yellow banner in the browser, which says "[We couldn't verify your license key for Telerik UI for Blazor. Please see the build log for details and resolution steps](#we-couldn-t-verify-your-license-key-for-telerik-ui-for-blazor-yellow-banner)".
2526

2627
Refer to the specific error messages and tips below.
2728

@@ -70,6 +71,12 @@ This error applies to subscription licenses. [Renew your subscription](https://w
7071

7172
[Purchase a commercial license to continue using Telerik UI for Blazor](https://www.telerik.com/purchase/blazor-ui).
7273

74+
### We couldn't verify your license key for Telerik UI for Blazor (yellow banner)
75+
76+
This section assumes an existing valid license key, so that the problem is not any of the above.
77+
78+
If you briefly see a yellow warning banner in the web browser that says "**We couldn't verify your license key**", then refer to [Using Telerik Packages in Referenced Projects](slug:installation-license-key#using-telerik-packages-in-referenced-projects).
79+
7380
## See Also
7481

7582
* [Download and Install License Key](slug:installation-license-key)

0 commit comments

Comments
 (0)