Our build pipeline recently broke in the Roslyn analyzers phase. Upon investigation, the problem was that the RulesMD project uses $(VisualStudioVersion), which gets redefined from 16.0 to 17.0 when the Roslyn analyzer task is run. Future versions of the Roslyn analyzer task will support 17.0, but the objective here is to unblock the pipeline. Once we move to the updated Roslyn analyzer, this PR should be backed out.
Validation run of this change can be found here. I canceled the build after the Roslyn step completed, since Roslyn was the only thing we were fixing.
Motivation
We need to be able to ship
Context
This change applies locally, meaning that the RulesMD project can only be built with VS2022. That shouldn't be a problem, since that's already our documented supported compiler version.
Details
Our build pipeline recently broke in the Roslyn analyzers phase. Upon investigation, the problem was that the
RulesMDproject uses$(VisualStudioVersion), which gets redefined from 16.0 to 17.0 when the Roslyn analyzer task is run. Future versions of the Roslyn analyzer task will support 17.0, but the objective here is to unblock the pipeline. Once we move to the updated Roslyn analyzer, this PR should be backed out.Validation run of this change can be found here. I canceled the build after the Roslyn step completed, since Roslyn was the only thing we were fixing.
Motivation
We need to be able to ship
Context
This change applies locally, meaning that the RulesMD project can only be built with VS2022. That shouldn't be a problem, since that's already our documented supported compiler version.
Pull request checklist