-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Update dotnet #1857
Comments
Hi, @tejasd1990! |
Hi @miketimofeev , I have added this issue for adding an announcement. My team owns the dotnetcore ecosystem, and we have made this change in the pr for the dotnet 5 release day 0 readiness. |
They have not yet been updated. We will be updating them soon. This is a hands-up to make folks aware of this change. Please update the message to call that out. |
hi @miketimofeev , we want to make this an announcement as I said earlier. Whats the way forward for that? |
@tejasd1990 , Alyona has create announcement in repository: #1891 |
@maxim-lobanov could you please update this issue after announcement is public this week? Would like to spread that information. |
Hello, I am closing this issue in favor of #1891. |
Tool information
Area for Triage:
Question, Bug, or Feature?:
Feature
Virtual environments affected
Can this tool be installed during the build?
Tool installation time in runtime
Are you willing to submit a PR?
yes #1856
Azure Pipelines hosted agents will soon be updated to contain .Net Core 5.x SDK/Runtime along with older lts versions. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions.
You can learn more about the breaking changes here:
https://docs.microsoft.com/en-us/dotnet/core/tools/
https://docs.microsoft.com/en-us/dotnet/core/compatibility/
To learn about more such changes and troubleshoot, refer here:
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting
The text was updated successfully, but these errors were encountered: