tag:blogger.com,1999:blog-24211979.post6878235865941633434..comments2022-12-04T19:07:42.160-07:00Comments on SageStorm Software Blog - a developers' life (as a dog): My Travels into the World of .NET CoreLiving and Working in Boisehttp://www.blogger.com/profile/03735204914740519136noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-24211979.post-31488595733079547302018-06-07T09:47:12.497-06:002018-06-07T09:47:12.497-06:00I don't get you Microsoft (or whoever is runni...I don't get you Microsoft (or whoever is running the releases for Microsoft.AspNetCore.All). Recently (06/2018), I got the errors when I engaged the nuget manager update tab in a solution that depended on Microsoft.AspNetCore.All, v2.0.<br />Error Package restore failed. Rolling back package changes for 'TimeCog.Server.Website'. <br />Error Package Microsoft.AspNetCore.All 2.1.0 is not compatible with netcoreapp2.0 (.NETCoreApp,Version=v2.0).<br />As you can see, Microsoft.AspNetCore.All was updated to v2.1.<br />Why would the IDE or the projects, for that matter, that depend on v2.0, care?<br />And why not install v2.1 side-by-side with v2.0 using the "Visual Studio Installer."<br />I do understand that after it's installed in a side-by-side manner, why you have to adjust each of the project's dependencies to use the new version. I get that.<br />But I don't understand the process imposed.Living and Working in Boisehttps://www.blogger.com/profile/03735204914740519136noreply@blogger.com