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: _contentTemplates/common/get-started.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,7 +199,7 @@ To download and install your Telerik license key:
199
199
1. Go to the <ahref="https://www.telerik.com/account/your-licenses/license-keys"target="_blank">License Keys page</a> in your Telerik account.
200
200
1. Click the **Download License Key** button.
201
201
1. Save the `telerik-license.txt` file to:
202
-
* (on Windows) `%AppData%\Telerik\telerik-license.txt`, for example, `C:\Users\...\AppData\Roaming\telerik-license.txt`
202
+
* (on Windows) `%AppData%\Telerik\telerik-license.txt`, for example, `C:\Users\...\AppData\Roaming\Telerik\telerik-license.txt`
203
203
* (on Mac or Linux) `~/.telerik/telerik-license.txt`, for example, `/Users/.../.telerik/telerik-license.txt`
204
204
205
205
This will make the license key available to all Telerik .NET apps that you develop on your local machine.
@@ -208,6 +208,6 @@ This will make the license key available to all Telerik .NET apps that you devel
208
208
209
209
#license-key-know-more-link
210
210
211
-
The [Telerik License Key](slug://installation-license-key) article provides additional details on installing and updating your Telerik license key in different scenarios.
211
+
The [Telerik License Key](slug://installation-license-key) article provides additional details on installing and updating your Telerik license key in different scenarios.[Automatic license key maintenance](slug://installation-license-key#automatic-installation) is more effective and recommended in the long run.
Copy file name to clipboardExpand all lines: getting-started/vs-code-integration/new-project-wizard.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,37 +44,41 @@ The available templates vary depending on the target framework and hosting model
44
44
45
45
Type your project name and select the output folder for it.
46
46
47
-
#### Section 3: Select UI for Blazor Version
47
+
#### Section 3: Install or Update License Key
48
+
49
+
If necessary, the Telerik Visual Studio Code extension will notify you about a missing or outdated [license key](slug://installation-license-key), and will install or update it.
50
+
51
+
#### Section 4: Select UI for Blazor Version
48
52
49
53
Select the preferred UI for Blazor version. Make sure that your system has access to the specified version of the UI components. You can achieve this with the [Telerik NuGet feed](slug://installation/nuget).
50
54
51
-
#### Section 4: Select Hosting Model
55
+
#### Section 5: Select Hosting Model
52
56
53
57
Here you can select the desired hosting model—[**WebApp**](slug://getting-started/web-app), [**Client** (also: WebAssembly)](slug://getting-started/client-side), [**Server**](slug://getting-started/server-side), or [**Hybrid** (a hybrid Blazor MAUI)](slug://getting-started/hybrid-blazor).
54
58
55
59
The available target framework options are updated upon selecting the hosting model.
56
60
57
-
#### Section 5: Select Your License Type
61
+
#### Section 6: Select Your License Type
58
62
59
63
Select your license type - **Commercial** (**Paid**) or **Trial**.
60
64
61
-
#### Section 6: Choose How to Distribute the Client Assets
65
+
#### Section 7: Choose How to Distribute the Client Assets
62
66
63
67
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).
64
68
65
-
#### Section 7: Enable or Disable Localization
69
+
#### Section 8: Enable or Disable Localization
66
70
67
71
Choose whether to use [localization](slug://globalization-localization) in the project or not.
68
72
69
-
#### Section 8: Select the Preferred Icon Type
73
+
#### Section 9: Select the Preferred Icon Type
70
74
71
75
Decide if you want to switch to using [Font Icons](slug://common-features-icons) instead of the default SVG icons.
72
76
73
-
#### Section 9: Select Target Framework
77
+
#### Section 10: Select Target Framework
74
78
75
79
The available .NET framework versions vary depending on the selected hosting model.
76
80
77
-
#### Section 10: Select Theme
81
+
#### Section 11: Select Theme
78
82
79
83
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).
Copy file name to clipboardExpand all lines: getting-started/vs-integration/convert-project-wizard.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ You can choose to back up the project state before the conversion (in a folder c
86
86
87
87
### Step 4: Install or Update License Key
88
88
89
-
If necessary, the Telerik Visual Studio extension will notify you about a missing or outdated [license key](slug://installation-license-key), and will help you resolve the issue.
89
+
If necessary, the Telerik Visual Studio extension will notify you about a missing or outdated [license key](slug://installation-license-key), and will install or update it.
Copy file name to clipboardExpand all lines: getting-started/vs-integration/new-project-wizard.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ Finally, you can apply one of the available [themes](slug://themes-overview) to
87
87
88
88
### Step 4: Install or Update License Key
89
89
90
-
If necessary, the Telerik Visual Studio extension will notify you about a missing or outdated [license key](slug://installation-license-key), and will help you resolve the issue.
90
+
If necessary, the Telerik Visual Studio extension will notify you about a missing or outdated [license key](slug://installation-license-key), and will install or update it.
Copy file name to clipboardExpand all lines: installation/license-key.md
+80-1Lines changed: 80 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,12 +51,91 @@ If you need to activate Telerik UI for Blazor only in a specific app, then save
51
51
52
52
## License Key Updates
53
53
54
-
Whenever you renew or purchase a new Telerik license, always install a new license key. The new license key includes information about all previous purchases. This process is referred to as a *license key update*.
54
+
Always install a new license key whenever you:
55
+
56
+
* renew or purchase a new Telerik license
57
+
* Start a new trial
58
+
The new license key includes information about all previous purchases. This process is referred to as a *license key update*.
55
59
56
60
* If you used [automatic license key installation](#automatic-installation), then open the tool that you used to download and install the license key file. You can also update the license key file by using the [manual steps above](#manual-installation).
57
61
* If you used the [manual license key installation](#manual-installation), then repeat the same steps.
58
62
* To [update your license key in CI/CD environments](slug://deployment-license-key), get your new license key and update the environment variable value.
59
63
64
+
## Frequently Asked Questions
65
+
66
+
#### Does the license key expire?
67
+
68
+
Yes, the license key expires at the end of your subscription:
69
+
70
+
* For trial users, this is at the end of your 30-day trial period.
71
+
* For commercial license holders, this is when your subscription term expires.
72
+
73
+
You need to download and install a new license key after:
74
+
75
+
* Starting a new trial
76
+
* Buying a new license
77
+
* Renewing an existing license
78
+
* Upgrading an existing license
79
+
80
+
An expired [perpetual license](https://www.telerik.com/purchase/faq/licensing-purchasing#licensing) key is valid for all Telerik UI for Blazor versions published before the license expiration date.
81
+
82
+
#### Will Telerik UI for Blazor function with an expired license key?
83
+
84
+
This depends on the [Telerik UI for Blazor license type (perpetual, subscription, or trial)](https://www.telerik.com/purchase/faq/licensing-purchasing#licensing):
85
+
86
+
**Perpetual licenses* function normally with an expired license key, as long as the application is using a version that was released before the expiration date of the license.
87
+
**Subscription licenses* function normally in already deployed applications, but you cannot rebuild and republish the app.
88
+
**Trial licenses* function normally only within the 30-day trial period.
89
+
90
+
Scenarios that do not match the above three descriptions result in the following application behaviors:
91
+
92
+
* A popup banner appears on application startup.
93
+
* A watermark appears on Telerik UI for Blazor components.
94
+
*[A warning message appears in the application's build log](slug://troubleshooting-license-key-errors).
95
+
96
+
#### I updated the Telerik UI for Blazor version in my project and license errors appeared. Why?
97
+
98
+
The most likely cause is that the new Telerik UI for Blazor version was released after the expiration date of your current license or license key. To fix this issue:
99
+
100
+
1. Renew your Telerik UI for Blazor license if necessary.
101
+
1.[Update your license key](slug://installation-license-key)
102
+
103
+
#### Can I use the same license key in multiple builds?
104
+
105
+
You can use your personal license key in multiple pipelines, builds, and environments. However, each individual developer must use their own unique personal license key.
106
+
107
+
#### Do I need an Internet connection to activate the license?
108
+
109
+
No, the license validation and activation occur offline.
110
+
111
+
#### Do I have to add the license key to source control?
112
+
113
+
No, you do not have to add the `telerik-license.txt` license key file or its contents to source control.
114
+
115
+
Build servers [must use the `TELERIK_LICENSE` environment variable](slug://deployment-license-key).
116
+
117
+
>warning Do not store the license key in plain text, for example, in a GitHub Actions Workflow definition.
118
+
119
+
#### What happens if both the environment variable and the license key file are present?
120
+
121
+
If both the `TELERIK_LICENSE` environment variable and the `telerik-license.txt` file are present, then the environment variable will be used.
122
+
To use the license key file, unset the environment variable.
123
+
124
+
#### What happens if several license key files exist?
125
+
126
+
If both a global and a project-specific `telerik-license.txt` files exist, then the project-specific license key will be used.
127
+
128
+
#### My team has more than one license holder. Which key do we have to use?
129
+
130
+
To activate Telerik UI for Blazor:
131
+
132
+
*[Every developer must be assigned their own license or seat](https://www.telerik.com/purchase/faq/licensing-purchasing).
133
+
* Every developer must use a license key that is associated with their personal Telerik account.
134
+
135
+
#### Are earlier Telerik UI for Blazor versions affected?
136
+
137
+
No, versions up to **7.1.0** released prior to February 2025 do not require a license key.
138
+
60
139
## Next Steps
61
140
62
141
*[Set Up the Telerik NuGet Feed](slug://installation/nuget)
0 commit comments