September 04, 2017

What’s new (Visual Studio 2017 image only)

The following changes were applied to Visual Studio 2017 image only:

  • #1762 Docker 17.06.1-ee-2
  • #1763 Docker images update (August 2017)
  • #1656 Docker: multi-stage builds
  • #1683 Visual Studio 2017 15.3.3
  • #1714 Node.js 8.4.0
  • #1742 .NET Core SDK 2.0.0 runtime x86 into Visual Studio 2017 image
  • #1747 InnoSetup 5.5.9 on Visual Studio 2017 Image
  • #1748 Go 1.9

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 2017

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

August 17, 2017

What’s new (Visual Studio 2017 image only)

The following changes were applied to Visual Studio 2017 image only:

  • #1683 Visual Studio 2017 15.3.0
  • #1729 .NET Core SDK 2.0
  • #1076 vcpkg (Microsoft VC++ Packaging Tool)
  • #1655 Git LFS 2.2.1
  • #1685 Go 1.7.6, 1.8.3
  • #1695 CMake 3.9.1
  • #1702 Azure Storage Emulator 5.2
  • #1710 Fixed: .csproj patching mistakenly skips files with TargetFrameworks tag
  • #1713 Git for Windows 2.14.1
  • #1714 Node.js 6.11.2, 8.3.0
  • #1718 NSIS 3.02.1
  • #1721 DirectX SDK on Visual Studio 2017 image
  • #1722 curl 7.55.1
  • #1723 Chrome 60.x
  • #1724 Chrome driver 2.31
  • #1725 Gecko driver 0.18.0
  • #1726 Firefox 55.0.2 (32-bit)
  • #1727 Selenium IE driver 3.5.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 2017

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

July 22, 2017

What’s new

  • #1657 Fixed: PowerShell performance regression
  • #1665 Fixed: * Missing C libraries: eay32, ssl32
  • #1666 Fixed: Start-BitsTransfer is not working
  • #1669 Fixed: Firewall regression for Rust builds
  • #1670 Fixed: Firewall rules regression for connecting SMB shares
  • #1671 Make OpenSSL 1.0.x branch the default option
  • #1672 Removed workaround for api.nuget.org
  • #1673 Centralized mechanism for delivering hotfixes to all build workers
  • #1676 Fixed: CLR Types Error when publishing DACPAC with msdeploy
  • #1677 Fixed: IE Selenium driver error on Visual Studio 2017 image
  • #1678 Visual Studio 2017 version 15.2 (26430.16)

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

July 19, 2017

What’s new

  • #1609 Full installation of OpenSsl on VS 2017 image
  • #1615 Fixed VS2017 regression: “Debugging tools for Windows” (part of Windows SDK) missing
  • #1617 Fixed: Multiple builds for single commit (GitLab)
  • #1619 OpenSSL 1.1.0f
  • #1625 Node.js 4.8.4, 6.11.1, 7.10.1, 8.1.4
  • #1627 Data-Tier Application Framework (17.1 DacFx) on Visual Studio 2017 image
  • #1629 Update VS 2017 Preview image to 15.3 Preview 3
  • #1635 Qt 5.9.1
  • #1639 .NET Framework 4.7 Developer Pack on Visual Studio 2015 image
  • #1641 Visual Studio 2017 version 15.2 (26430.15)
  • #1644 Fixed: NormalizedVersion is not supported in OData requests to NuGet feeds
  • #1648 Coverity Scan 2017.07
  • #1652 TypeScript 2.4.1 for Visual Studio 2015
  • #1660 Modify hosts file before install scripts

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

June 12, 2017

What’s new

  • #648 “Do not sync ACLs” setting for Web Deploy provider
  • #1350 Ruby 2.4.1-1
  • #1435 APPVEYOR_PULL_REQUEST_REPO_NAME and APPVEYOR_PULL_REQUEST_REPO_BRANCH variables
  • #1507 Artifacts: set content-disposition to instruct the browser about the filename
  • #1557 Chocolatey 0.10.7
  • #1576 Yarn 0.24.6
  • #1579 Fixed: UNC paths support regression
  • #1582 Fixed: PsExec regression
  • #1583 Node.js 6.11.0, 8.1.0
  • #1584 Fixed: Ping regression
  • #1585 Bundler v1.15.1
  • #1588 Qt 5.9
  • #1589 Azure PowerShell 4.1.0
  • #1590 Nuget 4.1.0
  • #1591 Azure Service Fabric SDK 2.6
  • #1593 Visual Studio 2017 version 15.2 (26430.13)
  • #1594 Fixed: AppVeyor Build Worker API PowerShell module is not in PSModulePath
  • #1596 CMake 3.8.2
  • #1597 Chrome 59.0.3071.86
  • #1598 Firefox 53.0.3
  • #1599 Chrome Driver 2.30
  • #1602 Fixed: clone_depth not working (on GitLab)
  • #1603 Gecko Driver 0.17.0
  • #1604 Cygwin 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