Reputation: 1545
I just checked my ASP.NET Core 2.0 packages in a project I am working on. I noticed that there are a series of updates from 2.0.0 to 2.0.1. I decided to update my packages. I started getting an error in updating as follows:
Detected package downgrade: Microsoft.NETCore.App from 2.0.3 to 2.0.0. Reference the package directly from the project to select a different version.
I go out into nuget and see that the Microsoft.NETCore.App package has indeed been updated to 2.0.3 3 days ago, but I am not trying to update that package. That package appears to be a dependent package for what I am trying to update. One of the packages I am trying to update is Microsoft.EntityFrameworkCore.Tools.DotNet from 2.0.0 to 2.0.1.
Any ideas on how to update? Should I just have some patience until some other packages roll out? I am guessing that with Microsoft.Connect() this week, there are a series of rollouts, but wanted to at least ask about this.
Thanks.
Upvotes: 0
Views: 495
Reputation: 19
I would recommend updating packages from commandline one by one in order of dependencies. That would clearly give error on package to be updated. You can use below query in package manager console: Update-Package [PackageName] -ProjectName [ProjectName] -Version [VersionToBeUpdated]
Upvotes: 1