Initial release of Visual Studio 2022 image:
- Based on Windows Server 2019.
- The software on the image is mostly identical to the one installed on
Visual Studio 2019 image. - WiX toolset is not installed on the image (related issue).
- Visual Studio 2022 is now 64-bit with installation location at
C:\Program Files\Microsoft Visual Studio\2022\Community. - Python 3.10 is now default in
PATH. - Ruby 3.0 is now default in
PATH.
What’s new
- Visual Studio 2022 Community Edition
- .NET Core 3.1.415, 5.0.403, 6.0.100
- Git 2.33.1
- Git LFS 3.0.2
- JDK 16.0.1, JDK 17.0.1
- PowerShell Core 7.2.0
Give Visual Studio 2022 image a try and let us know if anything’s missing.
What’s new
- Visual Studio 2019 version 16.11.5
- .NET Core 3.1.414, 5.0.402
- Python 3.10.0
- Google Chrome 95.0.4638.69
- Microsoft Edge 95.0.1020.40
- Firefox 93.0
- Go 1.17.2, 1.16.9
- CMake 3.21.4
- Qt 6.2.1
- PowerShell Core 7.1.5
- Apache Maven 3.8.3
Previous worker 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
What’s new
- #3706 Qt 6.1.3
- #3738 Qt 6.2.0
- #3707 Strawberry Perl 5.32.1.1
- #3710 Chocolatey v0.11.2
- #3713 NuGet v5.11.0
- #3715 Curl 7.79.1
- #3717 OpenSSL 3.0.0
- #3718 GitVersion 5.7.0
- #3729 Visual Studio 2019 version 16.11.3
- #3730 .NET Core 3.1.413, 5.0.401
- #3731 CMake 3.21.3
- #3732 Go 1.17.1, 1.16.8
- #3733 Firefox 92.0.1
- #3734 Google Chrome 94.0.4606.61
- #3735 Microsoft Edge 94.0.992.31
- #3736 Windows 11 WDK (10.0.22000.1)
- #3737 Windows 11 SDK (10.0.22000.1)
Other changes
- Qt 5.13.2 removed from the image
Previous worker 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
What’s new
- Visual Studio 2019 version 16.11.2
- Google Chrome 93.0.4577.63
- Microsoft Edge 92.0.902.84
- Firefox 91.0.2
- Go 1.17, 1.16.7, 1.15.15
- Python 3.9.7, 3.8.10, Pip 21.2.4
- CMake 3.21.2
- .NET Core 3.1.412, 5.0.400
- Ruby 3.0.2-1, 2.7.4-1 and 2.6.8-1
- PowerShell Core 7.1.4
- OpenSSL 1.1.1L
- LLVM 12.0.1
- Boost 1.77.0
- PostgreSQL 10.18, 11.13, 12.8, 13.4
- Node 16.8.0, 14.17.6, 12.22.6
Previous worker 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
What’s new in Ubuntu images
- .NET Core 3.1.412, 5.0.400
- Erlang 23.3.4.5
- AWS CLI 1.19.112
- Azure CLI 2.27.2
- Google Cloud SDK 355.0.0
- Python 3.7.11, 3.8.11, 3.9.6
- Go 1.17, 1.16.7, 1.15.15, 1.14.15
- CMake 3.21.2
- Node 16.8.0
- Packer 1.6.5
- Firefox 88.0.1
- Google Chrome 92.0.4515.159-1
Other changes
- Localstack has been removed
Previous worker images
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous UbuntuPrevious Ubuntu1604Previous Ubuntu1804Previous Ubuntu2004
You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml: