-
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
.NET 5.0 will become a default .NET version on December, 14 #1891
Comments
Is there a test branch to do some internal testing |
@ManuelGalindo unfortunately, this is not available in public yet and will become available after the official release. |
@ManuelGalindo we've delayed this by a week but you should be able to use |
Will this also include the required update of VS to 16.8? |
Could a date be confirmed please? I'd like to stop actively checking this and just add a date to my diary for when I can remove the UseDotNet step. Many thanks. |
Hi @DrGriff , |
if that is the recommendation, then there is no point having dotnet on the default image. also doesnt UseDotNet significantly slow down a build, and also waste a non trivial amount of resources? |
@SimonCropp UseDotNet adds 3 seconds on our Azure Hosted builds (because what we're after is already installed, but it will install it if it isn't) |
@MatthewSteeples what will the impact be when the default dotnet on the VMs is 5.1? |
Give Monday 14 Dec (aka Dec 14) 2020 then this fails with (SDK Version: 3.1.404)
We could add the installer, but whats the point? It takes time and if a latest .net fails, we want to know. Also, there is a side affect of using the installer that it changes the .net probing path so if you have 5.0 and 3.1 you need to install both Please update the agents with the latest .net 5.0 Thanks Update: |
@mikeblakeuk , based on our current deployment progress, Ubuntu images with .NET 5.0 will likely be fully deployed late 16th if there will be no unexpected issues. |
We didn't have any CI until now, so this is the bare minimum. Using the windows build agent as it has been updated to net5.0 (unlike linux, which is [currently in rollout](actions/runner-images#1891 (comment))). Note that ppy#4 should be merged first to fix a compilation error.
I've been experiencing intermittent issues restoring nuget packages on https://github.com/tgstation/tgstation-server/pull/1164/checks?check_run_id=15737103821
And many others |
Same for me, FWIW:
|
Related issue with work around actions/setup-dotnet#155 |
Avoid these errors that recently started appearing in GitHub actions Windows environment: ``` [...] D:\a\elm-fullstack\elm-fullstack\implement\PersistentProcess\PersistentProcess.WebHost\PersistentProcess.WebHost.csproj : error NU1101: Unable to find package Mono.Posix.NETStandard. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages [D:\a\elm-fullstack\elm-fullstack\implement\test-elm-fullstack\test-elm-fullstack.csproj] 34D:\a\elm-fullstack\elm-fullstack\implement\PersistentProcess\PersistentProcess.WebHost\PersistentProcess.WebHost.csproj : error NU1102: Unable to find package System.Collections.Immutable with version (>= 1.7.1) [D:\a\elm-fullstack\elm-fullstack\implement\test-elm-fullstack\test-elm-fullstack.csproj] 35D:\a\elm-fullstack\elm-fullstack\implement\PersistentProcess\PersistentProcess.WebHost\PersistentProcess.WebHost.csproj : error NU1102: - Found 2 version(s) in Microsoft Visual Studio Offline Packages [ Nearest version: 1.2.0 ] [D:\a\elm-fullstack\elm-fullstack\implement\test-elm-fullstack\test-elm-fullstack.csproj] 36Error: Process completed with exit code 1. ``` Integrate the workaround discovered by Jordan Brown, Gewoon Jaap, et al. For context, see: + actions/setup-dotnet#155 + actions/runner-images#1891
Images are deployed everywhere, if you see any issues - please, file a new ticket. |
Hi all, I'm learning ASP.NET CORE and getting this error while running the command "dotnet run" in my sandbox. Request you to kindly guide me here for the resolution. Many thanks! |
Breaking changes
.NET 5.0 will become a default .NET version on macOS and Ubuntu (Windows already contains .NET 5.0 as a default, it came along with Visual Studio 16.8)
Target date
Deployment of these changes will start on
December 7December, 14 and will take 3-4 days. (date is moved due to deployments freeze on a week of December, 7)The motivation for the changes
We would like to provide the latest .NET by default on images.
Possible impact
All pipelines that are not using actions/setup-net-core-sdk action for GitHub Actions or Use .NET Core task for Azure Pipelines might be affected due to a lot of possible breaking changes in new .NET version
Mitigation ways
Please consider using of actions/setup-net-core-sdk action for GitHub Actions or Use .NET Core task for Azure Pipelines to specify the needed .NET version.
The list of all available .NET versions can be found in corresponding documentation:
The text was updated successfully, but these errors were encountered: