-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET 5 support for dotnet core global tool #431
Comments
Even a release to bump to Core 3.1 will get onto an LTS with support until the end of next year :) |
What does this mean? Can we get a version that runs w/ later frameworks please? Never mind LTS. |
My point was that even if moving to .Net 5 was a bridge too far for some reason getting a version onto Core3.1 would mean support in base AzDo images for another 18 months (resolving the Core 2.1 EOL issue). I looked into upgrading and submitting a PR but ran into some issues I didn't know how to resolve so didn't get very far :( |
Sorry about lack of feedback here. I have released v 1.3.0 today, upgrading to .NET core 3.1. Upgrading to .net 5 or 6 is a taller order, I'm afraid, due to a lot of legacy dependencies. I have some different options here, going forward. Happy to discuss them |
FYI, @editim , grate, my/our built-from-scratch drop-in replacement (almost) for RoundhousE, is built on .NET 6 (rc2 at time of writing). https://erikbra.github.io/grate/ |
May be worth mentioning this on the homepage of this repo - I had to find this info by searching issues. |
Are there any plans to provide support for .NET 5 for roundhouse dotnet core global tool, before .NET Core 2.1 reaches EOL (August 21, 2021)?
The text was updated successfully, but these errors were encountered: