$ the-wire · showcase
Roslyn retires team-specific ExternalAccess assemblies
By RepoJournal · Filed · About .NET · Composed from the cited sources · methodology
Roslyn removed the team-specific ExternalAccess projects now that partner teams consume the unified EA, but ASP.NET keeps its EA until .NET 10 reaches end of life.
Roslyn removed the team-specific ExternalAccess assemblies now that partner teams have moved over to the unified EA [1]. Two exceptions survive. ASP.NET keeps its EA because an analyzer that ships in its SDK uses it, and it must still ship in hosts like MSBuildWorkspace and roslyn-language-server for as long as projects load against an older ASP.NET SDK, until .NET 10 reaches EOL [1]. EditorConfigGenerator's external access layer is gone entirely: the EditorConfig templates now live in Roslyn, so the template wizard composes the existing Roslyn option services directly through keyed IVTs from Features and Workspaces to Templates.Editorconfig.Wizard, and the external-access project, classes, type forwards, and packaging and build references are deleted [2]. Symbol publishing changes were intentionally left out of that removal [2][3].
In preparation for an upcoming parsing change rather than shipping one, Roslyn added syntax-tree baselines for partial modifier disambiguation covering modifier lists, member names, tuple return types, declaration kinds, and nested type positions. The tests record the parser's existing behavior and were run with ./.dotnet/dotnet test src/Compilers/CSharp/Test/Syntax/Microsoft.CodeAnalysis.CSharp.Syntax.UnitTests.csproj -f net10.0 --no-restore --filter FullyQualifiedName~ModifierParserRecoveryTests [4].
dotnet/performance fixed a CoreCLR WASM R2R perf payload failure from dotnet/runtime#130050 in runtime-wasm-perf build 1594255, Helix job 18f539fc-ed80-4f9b-bfc3-a37821338721 [5]. The cause was the .NET 11 to 12 rollover: the locally built WASM SDK, Crossgen2, and ILLink cohort is versioned 12.0.0-ci while the staged dotnet-none SDK carries Microsoft.NETCore.App at 12.0.0-alpha.1.26458.117, and the ILLink tool runtimeconfig requests 12.0 [5]. The fix materializes the SDK's installed Microsoft.NETCore.App framework under the exact local WebAssembly tool package version so ILLink can start without broad roll-forward settings [6].
The dotnet/dotnet codeflow pulled source updates from dotnet/roslyn [7], dotnet/efcore [8], and dotnet/sdk [9]. On the SDK desk, the dotnet-new details tests were serialized to prevent Helix hangs [10].
Action items
- → Check any tooling that referenced team-specific Roslyn ExternalAccess projects; only ASP.NET's EA remains dotnet/roslyn [plan]
- → Rebuild WASM ILLink perf payloads to pick up the framework version rollover fix dotnet/performance [monitor]
- → Run dotnet-new details tests against the serialization change before relying on Helix results dotnet/sdk [monitor]
References
- [1] Remove team specific ExternalAccess assemblies ↗ dotnet/roslyn
- [2] Remove EditorConfigGenerator external access layer ↗ dotnet/roslyn
- [3] Remove EditorConfigGenerator external access layer (#85207) ↗ dotnet/roslyn
- [4] Add partial modifier disambiguation parser tests ↗ dotnet/roslyn
- [5] [wasm] Handle local tool framework version rollover ↗ dotnet/performance
- [6] Fix WASM tool framework version rollover (#5310) ↗ dotnet/performance
- [7] [main] Source code updates from dotnet/roslyn ↗ dotnet/dotnet
- [8] [main] Source code updates from dotnet/efcore ↗ dotnet/dotnet
- [9] [main] Source code updates from dotnet/sdk (#9315) ↗ dotnet/dotnet
- [10] Serialize dotnet-new details tests to prevent Helix hangs (#56230) ↗ dotnet/sdk
