Windows images update on May 17, 2018

What’s new

  • #2325 NuGet 4.6.2 on Visual Studio 2017 image

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

Windows images update on May 16, 2018

Notable/breaking changes

  • #2246 Node.js 8.x is default installation now (because of Node.js 4 EOL). Modify appveyor.yml to get back to Node 4.x.
  • #2291 Qt 5.3, 5.4, 5.5, 5.7, 5.8 reached EOL were removed from VS 2015 image
  • #2289 Boost 1.56, 1.58, 1.59 removed from VS 2015 image
  • #2310 Visual Studio 2017 version 15.7.1

Other changes

  • #2325 Python 3.6.5 (with pip 10.0.1 pre-installed)
  • #2315 Python 2.7.15 (with pip 10.0.1 pre-installed)
  • #2195 Java 10
  • #2278 Azure CLI 2.0
  • #2281 CMake 3.11.1
  • #2275 Boost 1.67
  • #2324 TypeScript 2.8.3
  • #2233 .NET Core SDK 2.1.103, 2.1.104, 2.1.105
  • #2314 .NET Core SDK 2.1.200, 2.1.300-rc1
  • #2290 .NET 4.7.2 support
  • #2296 Windows SDK version 17134
  • #2309 LLVM 6.0
  • #2185 Qt 5.6.3
  • #2292 Qt 5.9.5
  • #2321 Service Fabric 6.2
  • #2186 Fixed: Android SDK v27 installation (Hyper-V image only)
  • #2227 Disable ‘VSIX Auto Update 15.6.152’ task
  • #2230 PowerShell Core 6.0.2
  • #2231 Fixed: CMake 3.11.0 breaks certain vcpkg builds
  • #2245 Mingw-w64 7.3.0
  • #2248 Update to Ruby 2.4.4 & 2.5.1
  • #2276 Node.js 10.1.0
  • #2282 Azure PowerShell 5.7
  • #2287 vcpkg 0.0.110
  • #2301 Cleanup Service Fabric environment
  • #2317 Visual Studio 2017 15.8 Preview 1
  • #2320 Fixed: Cannot RDP to build worker VM from Windows 10 machine
  • #2326 Miniconda2 4.5.1, Miniconda3 4.5.1

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

Windows images update on April 2, 2018

What’s new

  • #2178 vcpkg 0.0.107
  • #2180 CMake 3.11.0
  • #2199 Fixed: ASP.NET MVC pre-compiled views broken on latest Visual Studio 2017 image
  • #2210 Chrome 65.0
  • #2213 SQL Server 2016 SP1 CU8 (13.0.4474.0)
  • #2214 SSDT for Visual Studio 2017 (15.5.2)
  • #2219 Visual Studio 2017 version 15.6.4
  • #2220 Visual Studio 2017 Preview version 15.7.0 Preview 2.0
  • #2221 Firefox 59.0.2
  • #2222 Chrome Driver 2.37
  • #2223 Firefox Driver 0.19.1
  • #2224 IE Driver 3.9.0

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

Windows images update on March 15, 2018

What’s new

  • #2159 .NET Core 2.0.6 and .NET Core SDK 2.1.101
  • #2162 TypeScript 2.7.2 for Visual Studio 2015/2017
  • #2163 Visual Studio 2017 version 15.6.2
  • #2169 Fixed: Visual Studio 2015 image has Boost 1.65.1 built with Platform Toolset 141
  • #2170 Boost 1.66 to Visual Studio 2015 image

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

Windows images update on March 12, 2018

What’s new

  • #1845 New NuGet 4.1 publishing protocol
  • #1893 Optionally include jobs details into build history API
  • #1903 Allow package delete from project NuGet feed
  • #1964 Install vcpkg on ‘Visual Studio 2017 Preview image’
  • #1980 [Windows SDK] missing license file from the version #16299
  • #2045 Fixed: C:\Qt\5.9 link is broken
  • #2046 Qt 5.9.4
  • #2047 Compress C:\mingw-w64 on VS 2017 image
  • #2048 CMake 3.10 on VS 2017 Preview image
  • #2051 vcpkg 0.0.105
  • #2054 CosmosDB 1.20.91.1
  • #2058 Service Fabric 6.1
  • #2059 Visual Studio 2017 Installer Projects v0.8.6
  • #2060 Java 8 update 162
  • #2063 Fixed: Deployment Agent excessive thread usage
  • #2069 Random Roslyn exit issue
  • #2072 VC++ build failure
  • #2074 Fixed: MSYS2 builds broken
  • #2076 NSIS 3.03
  • #2081 Go 1.10
  • #2082 Qt 5.10.1
  • #2096 Boost 1.66
  • #2098 Boost 1.65.1
  • #2099 Yarn 1.5.1
  • #2102 Miniconda3 to 4.4.10
  • #2104 TypeScript 2.7 for Visual Studio 2015/2017
  • #2106 Enable strong crypto on build VMs
  • #2112 Visual Studio 2017 15.6.1
  • #2113 Azure Storage Emulator 5.3
  • #2114 Git 2.16.2
  • #2116 Disable VSIX Auto Update scheduled task
  • #2117 Node 6.13.1, 8.10.0, 9.8.0
  • #2118 Git LFS 2.4.0
  • #2119 Octo 4.31.3
  • #2120 Support for .net core 2.1 preview
  • #2121 Fixed: MSYS2 conflicting dependencies
  • #2122 Go 1.8.7, 1.9.4
  • #2127 Fixed: $isWindows and $isLinux is not set by Windows build agent
  • #2133 Cygwin 2.10.0
  • #2134 MSYS2 updated
  • #45 Elastic BeanStalk deployments
  • #1915 Fixed: ‘platform: Any CPU’ breaks ‘dotnet test’ execution
  • #2006 Octopus Deployment Provider
  • #2016 [deployment agent] run before- and after- deployment in separate process
  • #2050 Fixed: Empty ‘cache’ section makes whole build folder to be cached
  • #2066 Rolling Builds only for PRs
  • #2070 Fixed: AppVeyor looks for files with all extensions when looking for test assemblies
  • #2092 Fixed: Default configuration is missed with for/branches config
  • #2095 Fixed: Additional artifact is produced
  • #2141 Respect artifact type when package folder

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015