Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

What's the proper way to upgrade AspNetCore patch version?

See original GitHub issue

I’ve searched for this answer from some places and do not think I have a good answer for that. so I have the latest SDK installed. 222

And I new up a brand new AspNetCore empty project (using CLI or VS 2019) dotnet new web And now here is the screenshot from Nuget UI. 111

I can not select v2.2.5 from the dropdown list (on the right hand side), the dropdown is unselectable. I am just wondering what’s the proper way to update to the latest patch verison? I know that I can edit the *.csproj file do this <RuntimeFrameworkVersion>2.2.5</RuntimeFrameworkVersion> manually.

Is there any other way to do this? And I do not think manually change the patch version for the latest version is a good idea.

Another person had the same problem, without an answer either.

Thanks

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

2reactions

analogrelaycommented, May 15, 2019

If you are using .NET Core, the only thing you need to do to update to the patch is install the latest patched runtime on the machine running the app (i.e. your servers, dev boxes, etc.).

.NET Core applications automatically roll forward to the highest patch version associated with the major/minor pair you target. This behavior can be disabled using a setting in [appname].runtimeconfig.json but we strongly recommend you keep it to ensure you always run on the most up-to-date runtime (with all released security fixes).

While we do recommend you run on the latest patch, we recommend you do not update your app to target later patch versions as your app will fail to start if that patch doesn’t exist on the target machine. The version of Microsoft.AspNetCore.App you reference is a lower-bound, so if you reference 2.2.4 you’ll fail to start on a server that only has 2.2.3 installed. Patches shouldn’t be introducing APIs that you need to update to depend upon so there’s no need to update the package reference.

1reaction

analogrelaycommented, May 29, 2019

It’s not the clearest path to follow 😃. I would certainly be interested in any thoughts you have on how it can be clearer. If you didn’t find it, others might not either 😃