Skip to content

Commit 9105811

Browse files
authored
Update dpl-telerik-licensing-nuget-feed.md
1 parent 18a907f commit 9105811

File tree

1 file changed

+7
-15
lines changed

1 file changed

+7
-15
lines changed

knowledge-base/dpl-telerik-licensing-nuget-feed.md

Lines changed: 7 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to configure NuGet feeds to efficiently manage Telerik Do
44
type: how-to
55
page_title: Telerik.Licensing NuGet package is not available on the Telerik NuGet feed
66
slug: dpl-telerik-licensing-nuget-feed
7-
tags: telerik, document, processing, nuget, licensing, nuget, config
7+
tags: telerik, document, processing, nuget, licensing, feed, config, license, libraries, package, source
88
res_type: kb
99
ticketid: 1679127
1010
---
@@ -19,26 +19,18 @@ ticketid: 1679127
1919

2020
Starting with [2025.1.205 (2025 Q1)]({%slug release-notes-2025-1-205%}), all users of the Telerik and Kendo UI components and tools, will need to apply a valid license key file to both, new and existing projects. For details, see our [Licensing Documentation]({%slug license-key%}).
2121

22-
When working with Telerik Document Processing libraries, managing NuGet package sources efficiently becomes crucial, especially with the introduction of the **Telerik.Licensing** package. The Telerik NuGet Packages can be downloaded from the [Telerik NuGet Server]({%slug installation-nuget-packages%}#manually-download-nuget-packages). However, the **Telerik.Licensing** NuGet package is not available for downloading from the same feed.
22+
When working with Telerik Document Processing libraries, managing NuGet package sources efficiently becomes crucial, especially with the introduction of the **Telerik.Licensing** package. The Telerik NuGet Packages can be downloaded from the [Telerik NuGet Server]({%slug installation-nuget-packages%}#manually-download-nuget-packages). However, the **Telerik.Licensing** NuGet package is not available for download from the same feed.
2323

2424
This knowledge base article demonstrates how to configure NuGet package sources to facilitate smooth package restoration for both, Telerik Document Processing libraries and the Telerik.Licensing package.
2525

26-
This knowledge base article also answers the following questions:
27-
- How do I manage Telerik packages using the NuGet.config file?
26+
This knowledge-base article also answers the following questions:
27+
- How do I manage Telerik packages using the _NuGet.config_ file?
2828
- What is the best way to configure NuGet package sources for Telerik Document Processing libraries?
2929
- How can I ensure the Telerik.Licensing package is restored correctly in my projects?
3030

3131
## Solution
3232

33-
The [Telerik.Licensing NuGet package](https://www.nuget.org/packages/Telerik.Licensing) can be obtained through the `nuget.org` feed with **Package source**: *"https://api.nuget.org/v3/index.json"*. Indeed, it is not available for downloading from the Telerik NuGet feed.
34-
35-
However, there are advantages and disadvantages to uploading the Telerik.Licensing package to the Telerik NuGet Feed:
36-
37-
* **Pros**: indeed, it provides convenience for the clients, allowing them to download the NuGet package from the same source as the rest of the Telerik NuGet packages.
38-
39-
* **Cons**: With Q1 2025, all Telerik and Kendo UI products require the Telerik.Licensing NuGet package. As a result, the package will need to be uploaded separately for each product in the Download system, leading to duplication. Additionally, releasing a new version of Telerik.Licensing would require a corresponding new product release.
40-
41-
That is why it is a technical decision to have the **Telerik.Licensing** NuGet package **only** on nuget.org.
33+
With Q1 2025, all Telerik and Kendo UI products require the Telerik.Licensing NuGet package. The [Telerik.Licensing NuGet package](https://www.nuget.org/packages/Telerik.Licensing) can be obtained through the `nuget.org` feed with **Package source**: *"https://api.nuget.org/v3/index.json"* and is not available for download from the Telerik NuGet feed. **This prevents having to upload the package separately for each product in the Download system, which can lead to duplication and needing to do corresponding product releases.**
4234

4335
To ensure the Telerik.Licensing package and the Telerik Document Processing libraries are restored correctly, follow the steps below to configure your NuGet.config file:
4436

@@ -52,9 +44,9 @@ To ensure the Telerik.Licensing package and the Telerik Document Processing libr
5244
</packageSources>
5345
```
5446

55-
2\. **Ensure that your Telerik account** has the appropriate licenses and that you are authenticated correctly in the Telerik NuGet feed to avoid issues with accessing the Telerik Document Processing libraries.
47+
2\. Ensure that your **Telerik account** has the appropriate licenses and that you are authenticated correctly in the Telerik NuGet feed to avoid issues with accessing the Telerik Document Processing libraries.
5648

57-
3\. **For Continuous Integration (CI) environments**, ensure the Telerik.Licensing package is accessible via `nuget.org` and that the CI environment has access to the internet to restore the package. Alternatively, consider [manually downloading the NuGet packages]({%slug installation-nuget-packages%}#manually-download-nuget-packages) and hosting them in a local feed or directory accessible by your CI environment.
49+
3\. For **Continuous Integration (CI)** environments, ensure the Telerik.Licensing package is accessible via `nuget.org` and the CI environment has access to the internet to restore the package. Alternatively, consider [manually downloading the NuGet packages]({%slug installation-nuget-packages%}#manually-download-nuget-packages) and hosting them in a local feed or directory accessible by your CI environment.
5850

5951
By following these steps, you can efficiently manage the NuGet package sources for your projects that use Telerik Document Processing libraries and ensure the Telerik.Licensing package is restored correctly.
6052

0 commit comments

Comments
 (0)