Repository navigation
Move Verso to .NET 10 - #135
Merged
Merged
Conversation
.NET 8 reaches end of support on November 10, 2026, and .NET 9 ends the same day, so every project now targets net10.0 alone. The 1.2.2 release notes announced the move. Library packages lose their net8.0 build, and the CLI tool, the VS Code host, the Blazor apps, the samples, the showcases and the extension template are built for .NET 10. The PowerShell kernel moves to PowerShell 7.6.9, the release line built for .NET 10, which also clears the vulnerable System.Security.Cryptography.Xml it pulled in. PowerShell 7.6 depends on Roslyn 5, so the C# kernel moves from Roslyn 4.12 to 5.0.0 and C# cells get C# 14. ASP.NET Core Components moves to 10.0.14; EF Core, Sqlite, DependencyInjection and bunit move in tests only. F# cells can choose language version 10.0. On .NET 10 blazor.web.js is no longer embedded in the shared framework, so the CI step that extracted it from the .NET 8 assembly is gone. The CLI asks for the ASP.NET Core framework assets package and copies the script from there, failing the build when it is missing, and both workflows check that the packed tool carries it. Verso.Abstractions now validates its public surface against 1.2.3 on every build, ignoring only the dropped net8.0, so a change that would break existing extensions fails before it ships. The VS Code extension looks for the net10.0 host and asks for .NET 10 when none is found. A private .NET 8 runtime the extension installed earlier is no longer preferred over a newer .NET on PATH; it is forgotten when it cannot run the host. Signed-off-by: Torrey Betts <torrey.betts@gmail.com>
SummarySummary
CoverageVerso - 82.4%
Verso.Abstractions - 84.4%
Verso.Ado - 81.4%
Verso.Blazor - 31.4%
Verso.Blazor.Shared - 63%
Verso.Cli - 41.4%
Verso.DataFrame - 82.3%
Verso.FSharp - 83.5%
Verso.Host - 59.2%
Verso.Http - 76.2%
Verso.JavaScript - 59.8%
Verso.PowerShell - 64.7%
Verso.Python - 78.1%
Verso.Sample.Diagram - 80.1%
Verso.Sample.Dice - 82.2%
Verso.Sample.Slides - 58.8%
Verso.Sample.Sparkline - 67.3%
Verso.Testing - 79.4%
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
.NET 8 and .NET 9 both reach end of support on November 10, 2026, so as announced in the 1.2.2 release notes, this moves Verso to .NET 10 only. Every project now targets
net10.0: the library packages lose theirnet8.0build, and the CLI tool, the VS Code host, the Blazor apps, samples, showcases and the extension template are built for .NET 10. It ships as 1.3.0.Most of it is mechanical, but a few things moved with it:
net8.0, so a change that would break existing extensions fails before it ships. After 1.3.0 is out the baseline moves to 1.3.0 and the ignore goes away.net10.0host and asks for .NET 10 when none is found. A private .NET 8 the extension installed earlier was preferred overdotneton PATH, which would have shown a wrong "install .NET" prompt to anyone with .NET 10 already installed. It's now forgotten when it can't run the host.The one break for extension authors: a
net8.0project that floatsVerso.AbstractionsorVerso.Testingat1.*fails restore with NU1202 once 1.3.0 is published. They can move tonet10.0or pin 1.2.3. Extensions already published fornet8.0keep loading on the .NET 10 host.Verified locally:
dotnet test Verso.sln: 4082 passed, 0 failed, 8 skipped (ipywidgets tests); showcase tests 42/42; VS Code extension suite 69 passing, including 4 new tests for the runtime lookuplib/net10.0, and the CLI tool carriesblazor.web.jsverso servefrom build output, as an installed tool, and in production mode, with a C# cell run in the browserdotnet new verso-extensionwith every scaffold option createsnet10.0projects whose tests passNot verified locally: the missing-runtime dialog with only .NET 8 installed (covered by the new unit tests), and a release workflow dry run.