Visual Studio 2022 image is now available

Posted on November 10, 2021

A new Visual Studio 2022 image with Visual Studio 2022 and .NET 6 RTM is now available to all AppVeyor accounts:

  • The image is 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.

New and updated software

  • 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 how it worked for you!

Best regards,
AppVeyor team

Azure DevOps (VSTS) integration update

Posted on May 07, 2021

AppVeyor uses OAuth to access Azure DevOps resources. Azure DevOps removed obsolete authorization scopes from OAuth flow which broke the integration with AppVeyor. As a result some AppVeyor customers were unable to login with VSTS button or start new builds with VSTS repositories.

We deployed a fix and the customers should be able to re-authorize Azure DevOps on either “New project” or “Account > Authorization” pages. Unfortunately, we were unable to keep original OAuth app registration and had to create a new one, because scopes of existing app registration cannot be updated.

Best regards,
AppVeyor team

Follow us on Twitter: @appveyor

Artifacts retention policy update

Posted on March 30, 2021

To reduce AppVeyor hosting costs and eliminate any unnecessary waste of cloud resources back in 2018 we introduced artifacts retention policy.

The original policy was keeping paid account artifacts for 6 months and free account artifacts for 3 months. NuGet packages are kept intact.

Based on the feedback from our community we are changing artifacts retention period for paid accounts to 3 months and free accounts to 1 month. NuGet packages are kept intact.

This policy will take effect on April 5, 2021.

If you have custom requirements please let us know and we’ll discuss your needs.

Best regards,
AppVeyor team

Follow us on Twitter: @appveyor

.NET 5 and .NET Core SDK version pinning

Posted on November 14, 2020

With the recent update of Visual Studio 2019 image .NET 5 is now part of Visual Studio 2019 16.8 installation. Despite there is no more “Core” in “.NET 5”, technically .NET 5 is the next major release of .NET Core.

If your project does not have global.json then the latest .NET Core SDK is used which is now .NET 5. In theory, always using the latest version of .NET Core SDK should work, but if your build was broken or you are in the process of migrating to .NET 5 you may need to stick to a previous .NET Core SDK.

To build your projects with the latest .NET Core 3.1 add global.json to the root of project repository (or working folder from which dotnet or msbuild commands are run) with the following contents:

  "sdk": {
    "version": "3.1.102",
    "rollForward": "latestFeature"

And remember, there is Previous Visual Studio 2019 image with Visual Studio 2019 version 16.7.6 and without .NET 5. You can use it in case of any issues with the current image:

image: Previous Visual Studio 2019

Visual Studio 2019 Preview with .NET 5.0

Posted on September 29, 2020

.NET 5.0 has reached “RC” stage which means no more features will be added and it’s time to start testing your projects with .NET 5.0!

To help you start with .NET 5.0 development, we’ve baked the Visual Studio 2019 Preview image with the latest Visual Studio 2019 Preview and .NET 5.0.
In addition to VS 2019 Preview, it has the same software as on Visual Studio 2019 image.

You can select Visual Studio 2019 Preview image in “Build worker image” dropdown on Environment tab of project settings (if project configured on UI) or configure in appveyor.yml:

image: Visual Studio 2019 Preview