Visual Studio 2019 image update on January 9, 2020

What’s new

#1608 Setting up Visual Studio for debugging extensions. This one-time operation may take a minute or more.
#3245 Qt 5.14.0 on VS 2019 image
#3248 Qt 5.12.6 on VS 2019 image
#3251 GitLFS 2.9.2 on VS 2019 image
#3252 Octopus Tools 6.17.0 on VS 2019 image
#3253 Git 2.24 on VS 2019 image
#3254 PostgreSQL 12 on VS 2019 image
#3255 CMake 3.16.2 on VS 2019 image
#3256 Ninja 1.9.0 and Meson 0.52.1 on VS 2019 image
#3258 Visual Studio 2019 version 16.4.2
#3260 Install x86_64-8.1.0-posix-seh-rt_v6-rev0 on Visual Studio 2019 im
#3270 GitVersion 5.1.3 on VS 2019 image
#3272 Fixed: Visual Studio 2019 license has expired
#3273 OpenSSL 1.0.2u on VS 2019 image

There is a build worker image available from previous deployment. You can use it in case of any issues with the current image:

Previous Visual Studio 2019

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Visual Studio 2019

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Ubuntu

#3147 VS2019 and VS2019P: “find: ‘ ‘: No such file or directory”
#3185 Azure Cosmos DB Emulator to VS 2019 image
#3186 Golang to VS 2019 image
#3187 Fixed: AppVeyor cmdlets are not available in external PowerShell Core session on VS 2019 image
#3188 Fixed: xunit.console.clr4.x86 is not available on VS 2019 image
#3190 Azure PowerShell module to VS 2019 image
#3191 AWS PowerShell module on VS 2019 image
#3193 Rename WSL’s bash.exe in favor of Git’s bash.exe
#3198 Cygwin on VS 2019 image
#3199 Add Node.js development workload to VS 2019 image
#3228 GitVersion on VS 2019 image
#3229 Docker CE 19.03 on VS 2019 image
#3231 Visual Studio 2019 version 16.4
#3234 .NET Core SDK 3.1.100
#3235 .NET Core SDK 3.0.101, 2.2.207, 2.2.110

There is a build worker image available from previous deployment. You can use it in case of any issues with the current image:

Previous Visual Studio 2019

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Visual Studio 2019

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Ubuntu

#2040 Adding debug binaries to the Python installation
#3048 QT 5.9.8
#3052 vcpkg 2019.09.12-nohash
#3072 Chrome 78
#3085 Qt 5.13.2
#3094 LLVM (clang) 9.0.0
#3095 Qt 5.12.5
#3096 PowerShell Core 6.2.3
#3101 Cygwin 3.0.7
#3110 CosmosDB Emulator 2.7.0
#3142 Python 3.8.0
#3145 7-Zip 19.00
#3146 OpenSSL 1.0.2t, 1.1.0L, 1.1.1d
#3156 Go 1.13.3, 1.12.12, 1.11.13
#3157 Node 13.0
#3158 .NET Core SDK 2.2.109, 2.2.206, 2.2.402
#3165 Selenium drivers: Chrome 78.0, Gecko 0.26, IE 3.150.1
#3166 Firefox 70
#3167 Fixed: AppVeyor cmdlets are not available in external PowerShell session on VS 2019 image
#3168 Visual Studio 2017 version 15.9.17
#3169 CMake 3.15.5
#3170 Disable unnecessary services and background tasks on VS 2019 image
#3171 Python 2.7.17, 3.7.5
#3172 pip 19.3.1 for Python 2.7.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x
#3173 Miniconda 4.7.12.1
#3174 JDK 13 on VS 2015/2017 images
#3175 C++ 2019 Redistributable MSMs on VS 2019 image
#3177 Visual Studio 2019 version 16.3.8

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:

image: Previous Visual Studio 2017