These versions should not be used by any project that contributes to the design-time experience in VS, such as an analyzer, code-fix, or generator assembly.
Any tools that contribute to the design-time experience should use the MicrosoftCodeAnalysisVersion_LatestVS property above to ensure
For source generator support we need to target multiple versions of Roslyn in order to be able to run on older versions of Roslyn.
We pin these versions as we need to match them exactly for any scenarios that run Roslyn on .NET Framework, like Visual Studio.
...
...
@@ -40,19 +54,24 @@
It should never go ahead of the Roslyn version included in the SDK version in dotnet/arcade's global.json to avoid causing breaks in product construction.
<!-- Compatibility with the latest Visual Studio Preview release -->
<!--
TODO: Remove pinned version once arcade supplies a compiler that enables the repo to compile.
The exact version is always a moving target. This version should never go ahead of the version of Roslyn that is included in the most recent
public Visual Studio preview version. If it were to go ahead, then any components depending on this version would not work in Visual Studio
and would cause a major regression for any local development that depends on those components contributing to the build.
When we are building from source, we care more about reducing pre-built requirements than inner-loop dev experience, so we update this to be the same version
