Visual Studio 2015 was released more than a year ago, time proven on AppVeyor OSS environment and Visual Studio 2015 Update 1 was even released already. More and more customers use Visual Studio 2015 for their new projects and migrating existing projects into it. We at AppVeyor also use Visual Studio 2015 and find it very stable and mature enough to be installed on default build worker image.
Right now default build worker image has only Visual Studio 2013 installed and you have to wait if your project targets Visual Studio 2015 (Visual Studio 2015 is selected in “Build worker image” field of project settings or “os: Visual Studio 2015” added to appveyor.yml).
We are going to change default image to “Visual Studio 2015” for all existing accounts on Friday, March 18th, 2016.
After this change customers having “Visual Studio 2013” in “Build worker image” field on Environment tab of project settings (or “os:” setting in appveyor.yml does not contain “Visual Studio 2015” value, or no “os:” setting at all) will see some queue time increase between 1-2 minutes. This time is required to re-create and re-boot build worker VM with non-default image.
You may need to do a few easy steps below to fix that.
On “Environment” tab of project settings select “Visual Studio 2015” in “Build worker image” dropdown or if you configure your project through appveyor.yml add the following line to the config:
image: Visual Studio 2015
Even if your project targets Visual Studio 2013 or earlier you should still do this step because default image has both Visual Studio 2013 and Visual Studio 2015 installed.
Visual Studio 2015 comes with .NET 4.6.1 and MSBuild 14.0 which are upgrades to .NET 4.0 and MSBuild 12.0 respectively.
If your build calls msbuild.exe without specifying its full path and strongly depends on MSBuild 12.0 you may need to adjust PATH environment variable as “Visual Studio 2015” image has MSBuild 14.0 in PATH.
To change MSBuild path to MSBuild 12.0 add the following line to “Install” section of your project configuration:
for “CMD” mode:
set PATH=C:\Program Files (x86)\MSBuild\12.0\Bin;%PATH%
for “PS” mode:
$env:PATH="C:\Program Files (x86)\MSBuild\12.0\Bin;$env:PATH"
or add this command in install section of appveyor.yml:
install:
- set PATH=C:\Program Files (x86)\MSBuild\12.0\Bin;%PATH%
If you have any questions or concerns regarding this move please let us know by replying to this email or submitting a new issue on our forums.
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Windows Server 2012 R2Previous Visual Studio 2015You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:
os: Previous Windows Server 2012 R2
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Windows Server 2012 R2Previous Visual Studio 2015You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:
os: Previous Windows Server 2012 R2
There was a bug in Slack notification provider when AppVeyor was always prepending channel name with # and preventing sending notifications to private channels. Now, when that bug is fixed and AppVeyor is not adding # to a channel name anymore you may need to update your Slack notification settings to make sure public channel name starts with #. In appveyor.yml you need to quote channel name to pass YAML validation, for example:
- provider: Slack
auth_token:
secure: AAABBB+CCC==
channel: '#channel'
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Windows Server 2012 R2Previous Visual Studio 2015You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:
os: Previous Windows Server 2012 R2
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Windows Server 2012 R2Previous Visual Studio 2015You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:
os: Previous Windows Server 2012 R2