Tool information
Virtual environments affected
Can this tool be installed during the build?
Visual Studio cannot. The SDK can.
Are you willing to submit a PR?
If I knew how to update the virtual environment image, sure I'd be willing to do that...but I don't. If there are doc pointers I'll take a look.
We pull the latest version of VS that's available when we create the virtual environment. We're in the process of rolling out an update with VS16.4.0. VS16.4.1 will be included in an update following that.
@kaylangan This is great! Is there a public area for roadmap/rollout details?
Can this tool be installed during the build?
Visual Studio cannot. The SDK can.
Although .NET Core SDK can be installed individually, using msbuild to compile a .NET Core 3.1 project will fail, as older Visual Studio does not recognize or support some of the features in 3.1 projects. To correctly build a 3.1 project, it requires the VS 2019 16.4 to be installed.
@jozefizso for .NET Core projects, are you doing custom MSBuild items because you should be able to use dotnet build CLI command from the SDK to build Core projects.
I use the VSBuild@1 task to compile solution.
PS: projects target .NET 4.0, 4.7 and Core 3.1 simultaneously
@jozefizso got it, so you don't really need it for core, but your solution has other bits that require it. Makes sense. If your .NET Framework projects are SDK-style projects than they can be built using dotnet as well but I suspect they are not and are classic csproj.
FYI, I created https://github.com/actions/virtual-environments/pull/164 which updates Ubuntu 16.04 and 18.04 to include .NET Core 3.1.
VisualStudio/16.4.0+29519.181 and .NET Core SDK 3.1.100 are available now :) .
Most helpful comment
We pull the latest version of VS that's available when we create the virtual environment. We're in the process of rolling out an update with VS16.4.0. VS16.4.1 will be included in an update following that.