Turn on the Roslyn lexer by default for .NET 10 Razor projects#45808
Turn on the Roslyn lexer by default for .NET 10 Razor projects#45808333fred merged 3 commits intodotnet:mainfrom
Conversation
|
@dotnet/razor-compiler for reviews. |
|
Thanks for your PR, @333fred. |
97b8f91 to
8b00857
Compare
| <_TargetingNET90OrLater>true</_TargetingNET90OrLater> | ||
| <_TargetingNET100OrLater>true</_TargetingNET100OrLater> | ||
| <UseRazorSourceGenerator Condition="'$(Language)' == 'C#' AND '$(UseRazorSourceGenerator)' == '' ">true</UseRazorSourceGenerator> | ||
| <RazorLangVersion Condition="'$(RazorLangVersion)' == '' ">9.0</RazorLangVersion> |
There was a problem hiding this comment.
I assume this is intentionally 9.0 not 10.0 because we want to switch to newer lang version only later in the cycle?
There was a problem hiding this comment.
Correct; I also expect that putting 10.0 here would break until the razor compiler knows what that is.
|
@dotnet/product-construction, the unified builds are failing due to a missing JDK. Any idea what's going on? |
|
The JDK issue was fixed by #45822. |
|
Thanks @jkoritzinsky, merged in main. |
We want to turn on the new lexer by default for Razor projects targeting .NET 10, to get feedback on the experience as soon as possible. This enables that experience.