Upgrade to .NET 10 and refresh NuGet packages#338
Merged
Conversation
- TargetFramework: net8.0 -> net10.0 across all SDK-style projects (App, Core, Cli, Web, PlanShare, Tests). SSMS extension and its installer stay on net472 (VS extension constraint). - ModelContextProtocol/ModelContextProtocol.AspNetCore: 1.2.0 -> 1.3.0 - Microsoft.NET.Test.Sdk: 18.4.0 -> 18.5.1 - Microsoft.AspNetCore.Components.WebAssembly + DevServer: 8.0.12 -> 10.0.0 - CI workflows (ci, nightly, release, deploy-web): dotnet-version 8.0.x -> 10.0.x - Doc/comment refs to .NET 8 updated to .NET 10
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
1 participant
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.
Summary
TargetFrameworkfromnet8.0tonet10.0across all SDK-style projects (App, Core, Cli, Web, PlanShare, Tests). The SSMS extension and its installer stay onnet472— VS extensions still require .NET Framework.ModelContextProtocol1.2.0 → 1.3.0,Microsoft.NET.Test.Sdk18.4.0 → 18.5.1,Microsoft.AspNetCore.Components.WebAssembly(+ DevServer) 8.0.12 → 10.0.0.ci,nightly,release,deploy-web) bumped todotnet-version: 10.0.x..NET 8source comments updated to.NET 10.Mirrors the same .NET 10 upgrade exercise just completed on PerformanceMonitor. .NET 8 reaches end of support soon.
Test plan
dotnet build PlanViewer.sln -c Release— succeeds (6 pre-existing Avalonia 11.4 obsolescence warnings aboutDragEventArgs.Data/DataFormats.Files, unrelated to the framework bump)dotnet build server/PlanShare/PlanShare.csproj -c Release— cleandotnet test tests/PlanViewer.Core.Tests/PlanViewer.Core.Tests.csproj -c Release— 77/77 passing onnet10.0PlanViewer.App.exefrombin/Debug/net10.0/locally — opened cleanly