What happened to NuGet package Kendo.for.AspNet.Core?

[Ryan]

Our project has been using Kendo.for.AspNet.Core package since 2019, but it can't be found as of today.  And now our builds are all failing.

Here's a line from our dotnet restore that ran yesterday: "OK https://api.nuget.org/v3-flatcontainer/kendo.for.aspnet.core/index.json 142ms"

And here's the one that ran today: "NotFound https://api.nuget.org/v3-flatcontainer/kendo.for.aspnet.core/index.json 169ms".

Here's another error message we weren't getting yesterday: "error NU1101: Unable to find package Kendo.for.AspNet.Core. No packages exist with this id in source(s): NuGetOrg"

I would like to know what I could use to replace this package.  We were using the DataSourceRequest class it provided with our Kendo UI grids.

[Stacey]

Hello Ryan, 

 

Thank you for reaching out to us, I will pass this question to our product specialist to advise you further.

 

 

Regards, Stacey Progress Telerik

[Barry]

Our team is having the same problem.  We are trying to set up a new dev workstation, and the package is no longer available from the private Telerik nuget source.  Existing workstations seem ok, as I assume they have a local cache of the package. 

[Alexander]

Hi Barry,

The Telerik packages are distributed via a private NuGet feed - https://nuget.telerik.com/v3/index.json - and looking at your profile I see you should have access to the latest version and its packages. And looking at your profile I see you should have access to the latest version and its packages.

That said, searching for the exact name  - Kendo.for.AspNet.Core I see there was a package on NuGet, distributed by a third-party that is now indeed not available. If you are after the open source KendoUICore then it is available on NuGet here.

That being said personally, I would encourage you to upgrade to Telerik.UI.for.AspNet.Core NuGet you can review the following resource that you might find helpful in regards to this matter:

Installing with NuGet

[Barry]

Thank you Alexander.  As it turns out, we weren't using that package even though it was referenced in our project, so we simply removed the reference (it must have been an old artifact that we never cleaned up).