Tool information
Virtual environments affected
Can this tool be installed during the build?
No
Are you willing to submit a PR?
Potentially, if someone can point me in the right direction.
Visual Studio 2019 16.7 was released this month. We require 16.7 to build our product. Please update Azure Pipelines Microsoft Hosted Agents image "Windows Server 2019 with Visual Studio 2019 (windows-2019)" from Visual Studio 2019 16.6 to Visual Studio 2019 16.7.
Hello @kmahone !
We install latest VS on every image-generation. We have already started deployment of new image with VS 16.7, it should be deployed everywhere in 3-4 days: https://github.com/actions/virtual-environments/pull/1402
Perfect! Thanks for the quick response.
I've just run into this issue today which is blocking my PR. I understand I can fix it with a global.json file, however I can't seem to work out the correct version numbers. If I look on my local machine I see 3.1.6 (see below) however if I specify that in the globla.json file my project doesn't build. So what's a valid version I can use that works with < 16.7 of MSBuild? Alternatively what's the status of the rollout as I understand it started 5 days ago, how long does it take to deploy fully? Is there a status page we can look at?
Microsoft.AspNetCore.All 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
@dotnetprofessional I just tested 3.1.302 in the UseDotNet task and it seems to work for me.
@mattleibow Thanks that has solved my issue! :)
Hello everyone, small update: we had to stop deployment because of some regression with new VS version.
We are working to investigate the issue and will update this issue as soon as we have updates
Thanks for the update. So far, using the 3.1.302 version of .NET Core as part of the pipeline has been good and no other issues yet.
Thanks for the update @maxim-lobanov.
Did the workaround (use of 3.1.302) break today for anyone else or it's just me? I might have to change the pipeline to use .NET Core CLI instead of MSBuild/VS task. I'm guessing that should not fail, correct?
I use both. I set the UseDotNet and then use MSBuild.
Thanks, I was doing the same but it briefly stopped working for me (few hours today). Something must have been going on with the hosted build servers because the builds started succeeding after some time without any changes.
@hiraldesai , no changes from our side in this timeline (Friday is deployment freeze).
I believe you can check Image Version in Initialize Job step for failed and success builds. If image version is the same, VMs should be identical for builds
Thank you for your response @maxim-lobanov. Agent/Image details for both failed and successful build was this (windows-2019):
Current agent version: '2.173.0'
Current image version: '20200802.1'
Looking closely at the logs, build server image was not the issue (and it wasn't the MSBuild issue that this thread is referring to either) . Sorry I just assumed that it was the same MSBuild error resurfacing again without looking more into details.
This was the actual error I was getting briefly on Friday 8/21/2020 with "Use .Net Core 3.1.302" task. It resolved itself within couple of hours, so please ignore.
Hello, everyone!
VM image with Visual Studio 16.7.30413.136 has been deployed, readme updated
https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md
Most helpful comment
Hello everyone, small update: we had to stop deployment because of some regression with new VS version.
We are working to investigate the issue and will update this issue as soon as we have updates