This article explains how to install and use the NuGet feed and packages provided by Telerik to get the Telerik® UI for ASP.NET AJAX controls in your project.
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.
To use the UI for ASP.NET AJAX controls, you need to install ASP.NET Web Forms on your development/production machine. ASP.NET Web Forms is available in the .NET 4.0-4.8 installations.
If you enjoy how-to videos, take a look at the following video that demonstrates how to add the Telerik NuGet feed to Visual Studio.
If you prefer the written instructions, continue to the Telerik NuGet Feed in Visual Studio section.
Telerik provides a NuGet feed (package source) that you can add to Visual Studio. This allows you to quickly add the required Telerik packages to your project.
To configure the Telerik NuGet Feed in Visual Studio:
Open Visual Studio.
Go to Tools > NuGet Package Manager > Package Manager Settings, select Package Sources and then click the + button to add a new package source.
Enter a Name for the new package source, for example, Telerik NuGet.
Add the https://nuget.telerik.com/nuget URL as a Source 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, display the available packages, and install a package:
Create a new WebForms project or open an existing one.
Go to Tools > NuGet Package Manager > Manage NuGet Packages for Solution....
Select the Telerik NuGet Package source from the drop-down list on the left.
Select the Browse tab to see the available packages. This tab is called Online in older VS versions.
Enter your Telerik credentials in the Windows Authentication dialog.
Select the desired Telerik UI for ASP.NET AJAX package and click Install. To select the correct package version for your project:
- The .NET version of your project must correspond to the
.Net<version>portion of the package name. For example, the correct package for
.NET Framework 4projects is
- The .NET version of your project must correspond to the
The Telerik NuGet Feed allows you to install not only the UI for ASP.NET AJAX packages. You can also install packages that contain:
The following table lists the packages available in the Telerik NuGet Feed and the assemblies that they contain:
|NuGet package||Included assemblies|
|Telerik.UI.for.AspNet.Ajax.Netxx.xxxx.x.xxx.nupkg||Telerik.Web.Design.dll, Telerik.Web.Device.Detection.dll, Telerik.Web.UI.dll, Telerik.Web.UI.Skins.dll|
These libraries are available in the
AdditionalLibrariesfolder within the UI for ASP.NET AJAX installation directory.
You can download .nupkg files locally and build a private feed for your company.
Such a feed must be private (i.e., not available to the general Internet) and the standard developer-seat licensing model applies (i.e., the developers working with the controls must have active licenses). If you have questions on the licensing scheme, send them to email@example.com.
To download .nupkg files locally:
Navigate to Your Account.
Go to the Downloads page of UI for ASP.NET AJAX.
Click on the .nupkg files you require (e.g., Telerik.UI.for.AspNet.Ajax.Net45.2016.3.1027.nupkg) to download them. The file name is built in the following format:
Telerik.UI.for.AspNet.Ajax.Net<.NET version of your project>.<Telerik controls version>.nupkg.
Configure your server and projects to use the feed.
Often enough, you would want to set up Continuous Integration and/or Continuous Delivery (CI/CD) pipelines or builds for your project that uses the Telerik components. This is a valid scenario and the "one license per developer" license does not prevent you from doing so. The Telerik components are commercial software and as such can only be distributed through channels that are private and/or behind authentication.
There are a couple of common ways people implement CI/CD automated builds:
You can put your own credentials (or the credentials of the license holder, depending on how your licenses are set up) in the nuget.config of the build machine/pipeline. In many cases, when doing so, they will even be encrypted when you add the Telerik feed source through the CLI. Alternatively, you can copy an encrypted version from your own local config if you have one and if plain text is an issue. You can read more about adding credentials via the NuGet.config in the following page: https://docs.microsoft.com/en-us/nuget/schema/nuget-config-file#packagesourcecredentials.
Creating a local folder (for example, on a shared network drive or other suitable location accessible by your builds and team) that holds the
.nupkgfiles we provide (you can download them from your telerik.com account).
You must protect your credentials and ensure they are used only by you and not by other developers, according to the license-per-developer policy. For example, take your encrypted password from your local NuGet.config file and use it on the build PC. They can by such colleagues (like other developers, QAs, designers, front-end devs, DBAs and so on) for building and running a solution, provided they do not use the Telerik components to create functionality. Of course, you must ensure that such credentials or package sources are not available to the general public (for example, in public repositories).
Error details: Failed to fetch results from V2 feed at 'https://nuget.telerik.com/nuget/Packages' with following message : Response status code does not indicate success: 401 (Logon failed.).
The setup can get stuck in a circular reference problem if you enter incorrect credentials the first time. In order to reset or edit the nuget feed credentials:
- Close Visual Studio
- Open Control Panel -> All Control Panel Items -> Credential Manager or simply press Win button and type Manage Windows Credentials and open the manager.
- Look for VSCredentials_nuget.telerik.com -> remove or edit the password.
- Open Visual Studio and try to access the nuget.telerik.com feed again.
For additional troubleshooting options, see the NuGet can't connect to Telerik NuGet Server thread.
Make sure that the Telerik NuGet Feed is live at https://status.telerik.com/.
Error: The schema version of '
' is incompatible with version 2.0.30625.9003 of NuGet. Please upgrade NuGet to the latest version.
In R1 2018, the
nuget.exe version we use was updated from
4.3. This is the executable file used to generate and read the
Due to this update, you may get the error below when using Visual Studio 2012 that uses the NuGet Package Manager version 2.0. The solution is to upgrade the NuGet Package Manager to version 2.8.
Error: [Telerik NuGet] The V2 feed at 'https://nuget.telerik.com/nuget/Search()?$filter=IsLatestVersion&searchTerm='telerik'&targetFramework='net45'&includePrerelease=false&$skip=0&$top=26&semVerLevel=2.0.0' returned an unexpected status code '401 Logon failed.'.
See the following forum thread on the matter: nuget can't connect to Telerik NuGet Server.