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: licensing/license-key.md
+46-10Lines changed: 46 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,29 +9,44 @@ position: 1
9
9
10
10
# Setting Up Your Telerik UI for ASP.NET AJAX License Key
11
11
12
-
Starting with **2025 Q1**, Telerik UI for ASP.NET AJAX requires activation through a License Key. The `Telerik.Web.UI.dll` assembly now depends on `Telerik.Licensing.Runtime.dll` which can be obtained from NuGet ([https://www.nuget.org/packages/Telerik.Licensing](https://www.nuget.org/packages/Telerik.Licensing)) or from the Telerik UI for ASP.NET AJAX installations.
12
+
Starting with **2025 Q1**, Telerik UI for ASP.NET AJAX requires activation through a License Key. The `Telerik.Web.UI.dll` assembly now depends on `Telerik.Licensing.Runtime.dll`, available via NuGet ([https://www.nuget.org/packages/Telerik.Licensing](https://www.nuget.org/packages/Telerik.Licensing)) or the Telerik UI for ASP.NET AJAX installations.
13
13
14
-
This article describes how to download your personal license key and use it to activate the Telerik UI for ASP.NET AJAX components.
14
+
This article shows how to download your personal license key and activate Telerik UI for ASP.NET AJAX.
15
15
16
-
A missing or invalid license results in[errors and warnings]({%slug licensing/license-errors-warnings%}) during build and run-time indicators such as watermarks and banners.
16
+
If the license is missing or invalid, you will see[errors and warnings]({%slug licensing/license-errors-warnings%}) during build and run-time, such as watermarks and banners.
17
17
18
-
## Setup your License Key
18
+
## Choose your licensing method
19
19
20
-
Due to the differences between `Web Application Project`and `Web Site Project`, the steps to activate the license will differ.
20
+
Because Web Application and Web Site projects differ in structure, the activation steps also differ. Use the table below to quickly pick the correct method.
21
21
22
-
`Web Application Projects` have a `.csproj`/`.vbproj` file, whereas the `Web Site Projects` do not. For more details about the differences you can check out the following Microsoft documentation article: [Web Application Projects versus Web Site Projects in Visual Studio](https://learn.microsoft.com/en-us/previous-versions/aspnet/dd547590(v=vs.110)?redirectedfrom=MSDN).
| Web Application | Yes | License file (`telerik-license.txt`) |
25
+
| Web Application | No | Script key in `AssemblyInfo`|
26
+
| Web Site | No | Script key in `App_Code`|
27
+
28
+
> Quick check: If your project contains a `.csproj` or `.vbproj` file, it is a Web Application. Otherwise, it is a Web Site project. For additional background, see:
29
+
> -[Microsoft guidance: Web Application vs Web Site](https://learn.microsoft.com/en-us/previous-versions/aspnet/dd547590(v=vs.110)?redirectedfrom=MSDN)
30
+
> -[Web Site vs Web Application - Key Differences](https://www.youtube.com/watch?v=9gI6t57cDAc)
31
+
32
+
33
+
Now follow the activation steps for your project type:
23
34
24
35
### Web Applications using NuGet
25
36
26
-
Only for Web Application projects that have the `Telerik.UI.for.AspNet.Ajax.Net462` and `Telerik.Licensing`packages installed from NuGet, can be activated using a License File. Otherwise, an assembly attribute is required, see [Web Applications without NuGet and Web Sites](#web-applications-without-nuget-and-web-sites) section.
37
+
Only Web Application projects that have the `Telerik.Licensing`package installed from NuGet can be activated using a license file (`telerik-license.txt`). Otherwise, a Script key (assembly attribute) is required, see [Web Applications without NuGet and Web Sites](#web-applications-without-nuget-and-web-sites) section.
27
38
28
39
To download and install your Telerik license key file:
29
40
30
41
1. Go to the [License Keys](https://www.telerik.com/account/your-licenses/license-keys) page in your Telerik account.
31
42
2. Click the **Download License Key** button.
32
43
3. Save the `telerik-license.txt` file to your user profile directory `%AppData%\Telerik\telerik-license.txt`, for example, `C:\Users\...\AppData\Roaming\Telerik\telerik-license.txt`
33
44
34
-
>This will make the license key available to all Telerik applications that you develop on your local machine. If you need to activate Telerik UI for ASP.NET AJAX only in a specific application, save the `telerik-license.txt` to the root folder of this project or solution.
45
+
> This makes the license available to all Telerik applications on the local machine.
46
+
> To scope the license to a single project or solution, place `telerik-license.txt` in the root folder of that project or solution.
47
+
> The telerik-license.txt is applied during build and does not need to be deployed to the production server.
48
+
49
+
35
50
36
51
### Web Applications without NuGet and Web Sites
37
52
@@ -44,14 +59,35 @@ Web Applications projects that do not use NuGet and Web Site projects require an
44
59
-**Web Application**: Paste the copied key to the `Properties > AssemblyInfo` (C# Apps) or `My Project > AssemblyInfo` (VB Apps)
45
60
-**Web Site**: Add a C#/VB Class file to the `App_Code` directory of your project, e.g. `App_Code\TelerikLicense.cs` and paste the Script Key from your clipboard.
46
61
47
-
>To activate the license in other projects, repeat these steps.
62
+
> To activate the license in other projects, repeat these steps.
63
+
64
+
### License file vs Script key
65
+
-**License file** - supported for Web Application projects that use NuGet. It enables license validation during build and runtime.
66
+
-**Script key** - required for Web Applications that do not use NuGet and for Web Site projects.
67
+
68
+
> The license file method does not work for Web Site projects or for Web Applications that do not use NuGet. Use the Script key in these cases.
69
+
70
+
### How the license is applied based on project type
71
+
72
+
| Project Type | How license is applied | File needed on production server |
0 commit comments