Make MaxSupportedLangVersion calculation dynamic #75795
Conversation
dotnet-issue-labeler
bot
added
Area-Compilers
untriaged
dotnet-policy-service
bot
added
the
Community
|
see dotnet/templating#6781 (comment), every year we need to update this file when it's time to update the templates. for .net 10: dotnet/sdk#44349 @ViktorHofer @jcouv, how do you feel about this type of scalable approach? |
Uses historical trend to calculate language version based on the .NET version, removing hardcoded mappings. Ensures future .NET versions automatically align with expected C# version.
|
@jcouv want to make sure you've seen this. MSBuild logic looks good but you often do the lang version updates so want to make sure you see the new setup. |
| '$(_MaxSupportedLangVersion)' == ''">$([MSBuild]::Add(9, $([MSBuild]::Subtract($(_TargetFrameworkVersionWithoutV), 5)))).0</_MaxSupportedLangVersion> | ||
|
|
||
| <!-- Cap _MaxSupportedLangVersion if it exceeds _MaxAvailableLangVersion --> | ||
| <_MaxAvailableLangVersion>13.0</_MaxAvailableLangVersion> |
There was a problem hiding this comment.
@jcouv When a new language version is released, we'll just need to update _MaxAvailableLangVersion here and make adjustments in TargetTests.cs (updating the net10.0 line and adding a net11.0 line to match net10.0's language version). This setup means we won’t need to modify anything else for new framework versions released during this period each year.
There was a problem hiding this comment.
If we still need to update this file every year when we increase the max language version, then what do we actually save by making this change over the current system?
There was a problem hiding this comment.
The current system requires two updates each year: one when a new framework version is released (around October/November, managed by dotnet/sdk) and another when a new language version is added, which is handled in this repo. With this change, we're eliminating the need for the first update, as the framework version alignment will now happen automatically.
There was a problem hiding this comment.
I see. Thanks for clarifying for me. I'll let Julien be the second sign-off here though, since he does the roslyn-side of the process usually.
|
@jcouv for second sign off |
Uses historical trend to calculate language version based on the .NET version, removing hardcoded mappings. Ensures future .NET versions automatically align with expected C# version.