Nuget package Telerik.UI.for.AspNet.Core.Trial not found

1 Answer 12014 Views

Installer and VS Extensions

Voltus asked on 10 Nov 2017, 10:27 PM

capture.png

Hello support,

I want to use the Asp.Net Core extensions but I can't install the package Telerik.UI.for.AspNet.Core.Trial because it isn't found.

I followed the instructions at this link https://www.telerik.com/download-trial-file/v2/aspnet-core-ui but when I go to the option "Manage Nuget packages for solution" these are the packages available to download (see the attached file).

What can I do to install the package Telerik.UI.for.AspNet.Core.Trial?

Thank you.

1 Answer, 1 is accepted

answered on 13 Nov 2017, 08:20 AM

Hello Voltus,

In order to have access to the Telerik UI for ASP.NET Core, the Telerik Private Nuget feed has to be set up. Refer to the following NuGet Packages Documentation for detailed guide on how to configure it.

After the above step is successfully completed, restart Visual Studio in order for the new NuGet source to become available. Then, you should be able to install the Telerik.UI.for.AspNet.Core package by opening the NuGet Package Manager and then selecting the Telerik package source:

You can also refer to the Getting Started Documentation for further reference on configuring an ASP.NET Core project with Telerik UI for ASP.NET Core.

Regards,
Dimitar
Progress Telerik

Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.

Evan Weeks

commented on 08 Jan 2018, 02:46 PM

telerikpackagemissing.png

I've followed the instructions to set up telerik.com as a nuget source, but I still don't see the Telerik.UI.for.AspNet.Core package in the feed (see image). I've set up the source with my credentials, started the trial on the website, etc. This is an existing project I'm trying to get to build, and the only package missing is the telerik one.

Dimitar

commented on 11 Jan 2018, 09:48 AM

Hello Evan,

I have reviewed the provided screenshot and noticed that the Telerik UI for ASP.NET Core licensed version is being used in the project and you are licensed for the trial. Therefore, to integrate the version for which you are eligible, follow the steps below:

Remove the reference to the licensed version of the Kendo.Mvc.dll.
Open the NuGet Package Manager, select the Browse tab and search for the "Telerik.UI.for.AspNet.Core.Trial" package and install it.
Change the Scripts and Styles references in the _Layout.cshtml to point to the corresponding trial version that you have just installed.

For additional information on installing/configuring the Telerik UI for ASP.NET Core package with NuGet, please refer to the following documentation article.

Regards,
Dimitar
Progress Telerik

Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.

Mike

commented on 19 Jun 2018, 07:51 PM

I'm having a similar problem getting started. I get boxes with no styling when I try to use the Kendo controls. I tried to follow the post you referenced, but exactly where are we supposed to get the scripts and styles? Would you please post the code for a working _Layout.cshtml.

Mike

commented on 19 Jun 2018, 10:02 PM

OK. I didn't read the instructions well enough. It turns out the offensive code that prevents the styles from loading up is, in fact, the jquery scripts that the VS templates put in at the end of the <body> block.

Dimitar

commented on 20 Jun 2018, 10:58 AM

Hello Mike,

Yes, you are correct that this might lead to undesired side effects. The recommended way of loading the client side resources is to place them at the end of the <head> tag of the page. This is described in the Getting Started Article (point 8).

Regards,
Dimitar
Progress Telerik

Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.

Tom Oriel

commented on 27 Feb 2019, 09:42 PM

This works in a local development environment, but when trying to configure Continuous Integration (using AzureDevOps), my build consistently fails with the same error listed in the original post. how can this best be configured within Azure DevOps as part of a Continuous Integration Build

Dimitar

commented on 01 Mar 2019, 11:25 AM

Hello Tom Oriel,

In general, the Telerik UI for ASP.NET Core is distributed through a private NuGet feed. Therefore, in order to be able to successfully restore the package from Azure DevOps, the Telerik feed has to be correctly set up in Azure. Refer to the following resources that might be of help for configuring the feed:

Regards,
Dimitar
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.

Ahsan

commented on 16 Apr 2020, 07:42 PM

Hi Dimitar, I followed the instructions described in these two links:
https://docs.telerik.com/aspnet-core/knowledge-base/setup-private-nuget-feed-azure
https://docs.microsoft.com/en-us/azure/devops/artifacts/get-started-nuget?view=azure-devops&tabs=new-nav

but I am still getting the package failed to restore error on DevOps.

see the error below:
NU1101: Unable to find package Telerik.Documents.Flow.Trial. No packages exist with this id in source(s): NuGetOrg [

Dimitar

commented on 21 Apr 2020, 05:44 AM

Hello Ahsan,

The described error indicates that the Telerik Private NuGet Feed is not correctly setup, thus the package is not found. Please make sure that you have access to the private Feed locally by following these instructions. If that is indeed correct and you are able to correctly retrieve packages from Telerik NuGet Feed, then you should also be able to setup the feed for Azure as mentioned in the referred articles.

Regards,
Dimitar
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.