How to upgrade to 10.0.4xx? #56344

Activity

1. dotnetrepoman

   added

   dotnet-fundamentals/svc

   install/subsvc

   on Oct 8, 2026
2. dotnet-policy-service

   added

   ⌚ Not TriagedNot triagedNot triaged

   on Oct 8, 2026
3. BillWagner

   removed

   ⌚ Not TriagedNot triagedNot triaged

   on Oct 13, 2026
4. tevinch commented on Oct 27, 2026

   

   tevinch

   on Oct 27, 2026

   More actions

   10.0.112 and 10.0.4xx are different SDK feature bands. A current patch in the 1xx band can still be insufficient for the C# Dev Kit version discussed in #3619, where the maintainer required SDK 10.0.400 or later. Updating the runtime alone does not supply that SDK.

   apt update/apt upgrade only work with the candidates allowed by your configured package sources and policy. They do not establish that a 4xx SDK is available or that VS Code selected it. Start with:

   cat /etc/os-release
   apt-cache policy dotnet-sdk-10.0
   dotnet --list-sdks

   Then run dotnet --version from the solution directory and inspect its global.json and parent directories. Having a newer SDK installed is different from selecting it for a project.

   The official C# Dev Kit walkthrough has an SDK installation route. For APT, use the Ubuntu decision guide for your exact Ubuntu release and architecture; avoid mixing Microsoft and Ubuntu feeds. A separate non-admin SDK installation is another option, with its own dependency and update requirements.

   I put a step-by-step guide and small SDK-selection project here. It includes read-only package/path checks, an optional separate official 10.0.403 installation, and --version/MSBuild/build/run checks. A sample global.json using 10.0.400 with latestPatch selects an installed stable 4xx patch; it does not install one. Review your existing project's pin rather than replacing it automatically.

   After changing the SDK or pin, reopen the workspace and check Output → Projects for the SDK C# Dev Kit detects. The sample was verified with SDK 10.0.402 on macOS; Ubuntu APT, the Linux installation and Dev Kit's UI were not exercised, so this does not claim your machine's warning is resolved.