We understand this may impact your pipelines. If you are using vs2017-win2016 these are options to move forward:
– Start using the windows-2019 image. This image contains most of the tools (e.g. .NET Framework versions) currently available on vs2017-win2016.
This PR solves the problem by using the recommended image.
I chose 2022 and VS 2022 because that's what @AlwinEsch has been using for other add-ons.
Description
As title says, this updates the azure pipeline image to the recommended windows version.
According to https://devblogs.microsoft.com/devops/hosted-pipelines-image-deprecation:
This PR solves the problem by using the recommended image.
I chose 2022 and VS 2022 because that's what @AlwinEsch has been using for other add-ons.
How has this been tested?
Azure CI succeeds.