This article describes how to configure and use the Telerik NuGet feed.
NuGet is a popular .NET package manager. Telerik maintains a NuGet Feed with official UI for ASP.NET Core releases and service packs. These packages are available for registered users.
Our NuGet feed allows you instant access to various Telerik and Kendo packages that you can install in your project. Before you can use the Telerik NuGet Feed as a Package source, you must configure your machine by utilizing any of the following methods:
The improved Telerik NuGet v3 is now available for beta testing at https://nuget.telerik.com/v3/index.json. The new v3 API is faster, lighter, and reduces the number of requests from NuGet clients. You are welcome to try it.
The following video demonstrates how to add the Telerik NuGet feed through the NuGet Package Manager tool in Visual Studio or the
Open Visual Studio.
Go to Tools > NuGet Package Manager > Package Manager Settings, select Package Manager Sources, and then click the + button.
Add a Name for the Telerik NuGet feed.
Add the Source URL: https://nuget.telerik.com/nuget and click OK.
You have successfully added the Telerik NuGet feed as a Package source. The steps below describe how to authenticate your local NuGet instance and how to display the available packages:
Create a new project or open an existing project.
Right-click on the solution in the Solution Explorer window.
Select Manage NuGet Packages for Solution...
Select the Telerik NuGet Package source from the drop-down list.
Click on the Browse tab to see the available packages.
Enter your Telerik credentials in the Windows Authentication dialog.
You will see all packages that are licensed to your user account in the Visual Studio Package Manager.
- Download the latest NuGet executable.
- Open a command prompt and change the path to where the
Execute the command:
NuGet Sources Add -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "your login email" -Password "your password"
The above command stores a token in the
%AppData%\NuGet\NuGet.configfile. Your original credentials cannot be obtained from this token.
If you are unable to connect to the feed by using encrypted credentials, try the alternative approach of storing credentials in clear text:
``` NuGet Sources Add -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "your login email" -Password "your password" -StorePasswordInClearText ```
If you have already stored a token instead of storing the credentials as clear text, you could update the definition in the
%AppData%\NuGet\NuGet.config file using the following command:
``` NuGet Sources Update -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "your login email" -Password "your password" -StorePasswordInClearText ```
An alternative way to add the Telerik NuGet feed is to directly edit the
nuget.config file. You can read more about it in the Nuget Config File - Package Sources article.
Make sure you are familiar with how such configurations work. The Common NuGet Configurations article is a reference document you can use.
To use a
nuget.config file for the Telerik feed, you need to:
Ensure you have the relevant config file:
%AppData%\NuGet\NuGet.Config. You can create a new one by via the dotnet new command by calling
dotnet new nugetconfig.
Add the Telerik feed to it, and make sure to use plain-text credentials, because the .NET Core NuGet tooling does not fully support encrypted credentials. Here is an example of how your config file can look like:
<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <!--To inherit the global NuGet package sources remove the <clear/> line below --> <clear /> <add key="nuget" value="https://api.nuget.org/v3/index.json" /> <add key="telerik" value="https://nuget.telerik.com/nuget" /> </packageSources> <packageSourceCredentials> <telerik> <add key="Username" value="your telerik account email" /> <add key="ClearTextPassword" value="your plain text password" /> </telerik> </packageSourceCredentials> </configuration>
You could refer to this video for more details.
If you have already purchased a commercial Telerik UI license, you can use the Progress Control Panel application to configure the Telerik NuGet. Refer to this section in the Getting Started article for more details.
The UI for ASP.NET Core free trial installer package comes with an option that will automatically configure the Telerik NuGet feed for you. Refer to this section in the Getting Started article for more details.
The NuGet feed provides the following packages related to UI for ASP.NET Core and UI for ASP.NET MVC:
Telerik.UI.for.AspNet.Core—Telerik UI for ASP.NET Core Commercial.
Telerik.UI.for.AspNet.Core.Trial—Telerik UI for ASP.NET Core Trial.
Telerik.UI.for.AspNet.Mvc5—Telerik UI for ASP.NET MVC 5 Commercial.
Telerik.UI.for.AspNet.Mvc5.Trial—Telerik UI for ASP.NET MVC 5 Trial.
Telerik.UI.for.AspNet.Mvc4—Telerik UI for ASP.NET MVC 4 Commercial.
Telerik.UI.for.AspNet.Mvc4.Trial—Telerik UI for ASP.NET MVC 4 Trial.
Telerik.UI.for.AspNet.Mvc3—Telerik UI for ASP.NET MVC 3 Commercial.
Telerik.UI.for.AspNet.Mvc3.Trial—Telerik UI for ASP.NET MVC 3 Trial.
For more information on the list of the provided Kendo UI packages, refer to the article on installing Kendo UI for jQuery with NuGet.
This section provides solutions for common issues you might encounter while using the Kendo UI NuGet feed.
After changing my Telerik password, I get [Telerik Nuget] The V2 feed at '...' returned an unexpected status code '401 Logon failed.' error
After changing your Telerik password, you need to reset your credentials in the
NuGet.config file. To do this, run the
NuGet Sources Update -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" -UserName "your login email" -Password "your new password" command.
The password must contain only ASCII characters.
- Disable the auto-sync in the
_references.jsfile by modifying the following
/// <autosync enabled="false" />line.
- You can also disconnect the project from the source control before running the Update Wizard.
You may find useful the following Microsoft articles on securing your NuGet feed setup and supply chain as general best practices: