Open jmarolf opened 3 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
I propose we work with the compiler team on option number 1.
Design meeting conclusion: We should provide more meaningful errors to cusotmers when such a scenario occurs.
@jmarolf Is this considered fixed with https://github.com/dotnet/roslyn/pull/61261 ?
If the user sets
<EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
then they will load in the Roslyn code style assemblies.The CodeStyle layer references the latest version of the roslyn compiler. This has worked great for now. .NET SDK 5.0.300 is only compatible with Visual Studio 16.11 so the compiler versions match in both the SDK and Visual Studio.
The question is: what should happen if the user installs a newer SDK and uses them with an older Visual Studio. Today if the user installs a .NET 6 preview SDK that will contain the 4.0 compiler, but no versions of Visual Studio exist that ship with that compiler today.