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: docs-aspnet/backwards-compatibility/2025-backwards-compatibility.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,21 @@ This article lists the breaking or important changes in the 2025 releases of {{
16
16
17
17
The ActionSheet's action buttons now accept enums for the `FillMode`, `Rounded`, `ThemeColor`, `Size` properties instead of strings. The `ActionSheetItem.Group` property now accepts the `ActionSheetItemGroup` enum instead of a string.
18
18
19
+
{% if site.core %}
20
+
### TabStrip
21
+
22
+
In versions before 2025 Q3, the `icon-class` configuration option sets a sprite CSS class in the items of the TabStrip TagHelper. Starting with version 2025 Q3, the `icon-class` attribute applies a custom CSS class to the default SVG tab icon element. The `sprite-css-classes` attribute sets sprite icons to the TabStrip tabs.
Copy file name to clipboardExpand all lines: docs-aspnet/html-helpers/navigation/tabstrip/images.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ To include images in the Telerik UI for {{ site.framework }} TabStrip items, use
66
66
67
67
## Sprites
68
68
69
-
To include sprites in the Telerik UI for {{ site.framework }} TabStrip items, use the `.SpriteCssClasses()` configuration option and specify the sprite CSS class:
69
+
To include sprites in the Telerik UI for {{ site.framework }} TabStrip items, use the `.SpriteCssClasses()` configuration option and specify the sprite CSS class:
70
70
71
71
```HtmlHelper
72
72
@(Html.Kendo().TabStrip()
@@ -98,27 +98,26 @@ To include sprites in the Telerik UI for {{ site.framework }} TabStrip items, us
The Netherlands is a constituent country of the Kingdom of the Netherlands, located mainly in North-West Europe and with several islands in the Caribbean.
117
114
</content>
118
115
</tabstrip-item>
119
116
</items>
120
117
</kendo-tabstrip>
121
118
```
119
+
120
+
> Note: In versions before 2025 Q3, the `icon-class` configuration option sets a sprite CSS class in the items of the TabStrip TagHelper. Starting with version 2025 Q3, the `icon-class` attribute applies a custom CSS class to the default SVG tab icon element. The `sprite-css-classes` attribute sets sprite icons to the TabStrip tabs.
description: "Learn the answers to frequently asked questions about the {{ site.product }} licensing."
5
5
slug: licensing-faq
6
+
previous_url: /licensing
6
7
position: 3
7
8
---
8
9
9
10
# Frequently Asked Questions
10
11
11
-
This article lists the answers to the most frequently asked questions (FAQs) about working with the {{ site.product }} license key.
12
+
This article lists the answers to the most frequently asked questions (FAQs) about {{ site.product }} licensing.
13
+
14
+
## What types of licenses are available for {{ site.product }}?
15
+
16
+
Progress<sup>®</sup> {{ site.product }} is available under a developer (commercial) or a trial license.
17
+
18
+
Regardless of the license version you hold, to use {{ site.product }}, you have to activate a license key and agree to the [End User License Agreement](https://www.telerik.com/purchase/license-agreement/kendo-ui).
19
+
20
+
You can find the license agreement in your Telerik controls installation folder under `\license-agreements\EULA.rtf`. For example, the default location for the Q4 2024 release is `C:\Program Files (x86)\Progress\{{ site.product }} 2024 Q4\license-agreements\EULA.rtf`.
21
+
22
+
## What is the current licensing mechanism?
23
+
24
+
Starting with the 2025 Q1 release, {{ site.product }} requires activation through a license key (trial or commercial). To download your personal activation key and activate the {{ site.product }} components, follow [License Key Installation]({%slug installation_license_key_aspnetcore%}) steps.
25
+
26
+
An invalid license results in [errors and warnings]({%slug troubleshooting-license-key-errors%}) during build and run-time indicators such as watermarks and banners.
12
27
13
28
## Does the license key expire?
14
29
@@ -81,7 +96,21 @@ To activate {{ site.product }} in a CI/CD environment, use any of the license ke
81
96
82
97
## Are earlier {{ site.product }} versions affected?
83
98
84
-
No, versions up to **2024.4.1112** released prior to February 2025 do not require a license key. They use an older licsensing mechanism that requires [Referencing a Script Key]({%slug installation_legacy_licensing_aspnetcore%})
99
+
No, versions up to **2024.4.1112** released prior to February 2025 do not require a license key. They use an older licensing mechanism that requires [Referencing a Script Key]({%slug installation_legacy_licensing_aspnetcore%})
100
+
101
+
## What about the license.licx file in old product versions?
102
+
103
+
As of the Q1 2015 release, Telerik® {{ site.product_short }} uses the standard .NET licensing mechanism—if you use Telerik® {{ site.product_short }} items in design-time, Visual Studio adds a `license.licx` file to the solution. This file is used only in design-mode and is not needed for deployment explicitly. The .NET framework (`lc.exe`) will embed it in the assembly when your application is built for deployment.
104
+
105
+
The `license.licx` license file is maintained by Visual Studio and contains information about all licensed components in the application, including non-Telerik products. Having this license file is not expected to bring any performance or compilation issues and you can ignore it.
106
+
107
+
If your project build fails with errors which point to the license file, you can delete it and rebuild. Alternatively, you can clear its contents and mark it as **Read Only**.
108
+
109
+
If you are working under source control, once the file is created, it will be detected as a change by your source control system. Telerik suggests that you check in this file initially. When the file is checked out again during your work, it is up to you to decide whether to check it in, or discard the changes.
110
+
111
+
## Where can I find information about Bill of Materials (BOM) and third-party software licenses?
112
+
113
+
You can find a Bill of Materials (BOM) and a list of the third-party software, including open-source software, in the `\LicenseAgreements\ThirdParty\NOTICE.txt` location in your Telerik controls installation folder. For example, the default location for the Q4 2024 release is `C:\Program Files (x86)\Progress\{{ site.product }} 2024 Q4\license-agreements\third-party\NOTICE.txt`. For versions prior to R2 2018 SP1, the file is called `licenses.txt`.
0 commit comments