This article explains how to add the private Telerik NuGet feed to your system. You can use it to obtain the Telerik UI for Blazor components.
There are several approaches:
This article also offers some troubleshooting information in case you encounter problems:
The following video explains how you can add the Telerik NuGet feed. If you prefer to do this yourself, follow the rest of this article.
To add the Telerik private NuGet feed, follow the steps below:
- Download the latest NuGet executable. If you cannot use the
exe(for example on Mac or Linux), you can use a nuget.config file.
- Open a Command Prompt and change the path to where the
- Execute the command from the example below.
The command from the example below stores the password in clear text in the
%AppData%\NuGet\NuGet.config file. If you are unable to connect to the feed using encrypted credentials, use this alternative approach.
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, update the definition in the
%AppData%\NuGet\NuGet.config file by using the command below.
NuGet Sources Update -Name "telerik.com" -Source "https://nuget.telerik.com/nuget" ^ -UserName "your login email" -Password "your password" ^ -StorePasswordInClearText
The ASP.NET Core tooling does not fully support encrypted credentials.
NuGet feeds and other settings can be stored in a
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 tooling does not fully support encypted 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>
This section lists problems related to the Telerik NuGet feed and their solutions
There are two common reasons for the Telerik packages to be missing in the Telerik Online Feed:
There is a network issue. For example, a proxy, firewall or other similar software blocks requests to our server.
Your license is tied to a different account than the one used for the feed credentials.
To check if this is a networking issue, open the following URL in your browser and enter your
telerik.com credentials: https://nuget.telerik.com/nuget/Search()?$filter=IsAbsoluteLatestVersion&searchTerm=%27Blazor%27&includePrerelease=true&$skip=0&$top=100&semVerLevel=2.0.0. You should see an XML result with the list of packages you can access and you should see the
Telerik.UI.for.Blazor package with the version appropriate to your license.
If you can access the feed in the browser, but you do not see the packages in Visual Studio, the most likely problem is wrong credentials that are not associated with a license.
Here is a sample process of removing stored credentials from Windows so you can re-add the correct ones:
- Remove saved credentials in Windows Credential Manager. They will appear as nuget.telerik.com and/or VSCredentials_nuget.telerik.com entries.
- Remove the Telerik Nuget package source from Visual Studio.
- If you have added the Telerik package source by nuget CLI, then try to remove it from the CLI.
- Check if there are any credentials stored in
%AppData%\NuGet\Nuget.Configand if so you have to remove them.
- Try to reset Visual Studio user data. You can read how to do that here.
- Restart Visual Studio.
- Enter the Telerik nuget package source again through Visual Studio or CLI. If you are using the feed in .NET Core application, store your credentials as plain text.
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.
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/or the Telerik packages and ensure they are used only by you and not by other developers, according to the license-per-developer policy. 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).
When using Azure pipelines, we encourage you to review the following blog post on setting things up: Azure DevOps and Telerik NuGet Packages.
There are a couple of common questions and issues:
Obtaining credentials - see the points above for either using your own credentials, or using a shared package source.
Telerik feed not being found - the most common reason for a problem is that the path to the
nuget.configfile is wrong (it should, by default, be at the root level).
index.json not founderror can occur from many root causes. If you have successfully authenticated, this error usually means that the feed wasn't able to be searched or connected to. A common reason is an incorrect feed URL, such as including a trailing slash - Correct:
https://nuget.telerik.com/nuget/, or a connectivity issue such as a firewall rule in your organization.