This article explains how to use the NuGet feed and packages provided by Telerik to get the Telerik® UI for ASP.NET AJAX controls in your project.
This feed is available as of Q3 2015 SP1 (ver. 2015.3.1111).
This article contains the following sections:
- How to use the Telerik NuGet feed in Visual Studio
- Available Telerik Nuget packages and the ddls in them
- How to download a .nupkg file to create local feeds
- Telerik NuGet feed and automated builds
Prerequisite In order to have the Telerik® UI for ASP.NET AJAX running, you will need to have ASP.NET AJAX installed on your development/production machine.
Telerik provides a NuGet feed that you can use in Visual Studio by following these steps:
Open Visual Studio.
Go to Tools > NuGet Package Manager > Package Manager Settings, select Package Manager Sources and then click the + button to add a feed.
Add a feed with the following URL: https://nuget.telerik.com/nuget and click OK.
Create or load your WebForms project.
Go to Tools > NuGet Package Manager > Manage NuGet Packages for solution.
Choose the Online / Browse list of packages (depending on your VS version).
Enter your Telerik credentials in the Windows Authentication dialog (e.g., user: firstname.lastname@example.org and password: myPassPhraseForTelerikDotCom).
You can enter your credentials only once by selecting the Remember my password checkbox.
Select the Telerik® UI for ASP.NET AJAX package, e.g., Telerik.UI.for.AspNet.Ajax.Net45) and click Install. The package name is built in the following format:
Telerik.UI.for.AspNet.Ajax.Net<.NET version of your project>and you should make sure to select the desired Telerik version.
Search for "telerik.ui.for" to narrow down the list of results and find the package easily.
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
Telerik.Windows.Zip.xxxx.x.xxx.nupkg - Telerik.Windows.Zip.dll
Telerik.Windows.Zip.Extensions.xxxx.x.xxx.nupkg - Telerik.Windows.Zip.Extensions.dll
Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.xxxx.x.xxx.nupkg - Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.dll
Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.xxxx.x.xxx.nupkg - Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.dll
Telerik.Windows.Documents.Spreadsheet.xxxxx.x.xxx.nupkg - Telerik.Windows.Documents.Spreadsheet.dll
Telerik.Windows.Documents.Flow.FormatProviders.Pdf.xxxx.x.xxx.nupkg - Telerik.Windows.Documents.Flow.FormatProviders.Pdf.dll
Telerik.Windows.Documents.Flow.xxxxx.x.xxx.nupkg - Telerik.Windows.Documents.Flow.dll
Telerik.Windows.Documents.Fixed.xxxxx.x.xxx.nupkg - Telerik.Windows.Documents.Fixed.dll
Telerik.Windows.Documents.Core.xxxxx.x.xxx4.nupkg - Telerik.Windows.Documents.Core.dll
Telerik.Documents.SpreadsheetStreaming.xxxxx.x.xxx.nupkg - Telerik.Documents.SpreadsheetStreaming.dll
Newtonsoft.Json - Newtonsoft.Json.dll - available for download from the nuget.org server.
Telerik.Web.Spreadsheet.nupkg - not yet available as a nuget package. You can also obtain the Telerik.Web.Spreadsheet.dll from the AdditionalLibraries/Bin40 installation folder.
You can download a .nupkg file to build a private feed for your company by following the steps below.
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.
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.
If you are using the Telerik NuGet feed on an automated build environment, you can provide your own credentials to the build PC so that it can connect to the feed and download the package.
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.
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.
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.
The schema version of
'<namespace>'is incompatible with version 2.0.30625.9003 of NuGet. Please upgrade NuGet to the latest version.