Repository navigation
Upgrade build to .NET 10 and thus raise minimum PS7 version to 7.6 - #2266
Christoph Bergmeister (bergmeister) with Copilot wants to merge 9 commits into
Conversation
Co-authored-by: bergmeister <9250262+bergmeister@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are reported for the .NET 10 build and development environment update.
No open issues 🎉
What changed in this PR
Updates the build and development environment to .NET 10 ahead of .NET 8’s end of support, addressing #2195 while leaving runtime targets unchanged.
Changes:
- Pins the SDK to
10.0.401, retaininglatestFeatureroll-forward. - Updates the devcontainer image and display name to .NET 10.
- Refreshes README requirements to .NET 10 and Visual Studio 2026.
| File | Description |
|---|---|
| README.md | Updates SDK and recommended Visual Studio requirements. |
| global.json | Pins the build SDK to 10.0.401. |
| .devcontainer/Dockerfile | Switches the container base image to .NET 10. |
| .devcontainer/devcontainer.json | Updates the container display name to .NET 10. |
Review effort: Balanced
Co-authored-by: bergmeister <9250262+bergmeister@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Copilot upgrading .NET from 8 to 10 also means upgrading the minimum supported version of PowerShell 7 version from 7.4 to 6.6 as we have tests for that in our manifest script (.psdm1 file). Please update it and other places that referenced PowerShell 7.4 |
Co-authored-by: bergmeister <9250262+bergmeister@users.noreply.github.com>
Updated the module loader minimum to PowerShell 7.6.6 in b0be65a. I kept the SMA 7.4.14 reference because SMA 7.6.6 targets only net10, while this project retains its net8 target; the net8 Engine build and focused tests pass. |
|
Copilot why not powershell 7.6.9? it's latest powershell version and by the time psscriptanalyzer releases it would've been out for long enough as guidance is to update powershell within a month after release of patch. alos, I think we should update SMA reference and update everyting that targets net8 to net10 because net10 is implicitly the minomum .NET version due to the minimumm PowerShell 7 upgrade to 7.6 |
Co-authored-by: bergmeister <9250262+bergmeister@users.noreply.github.com>
Updated to PowerShell/SMA 7.6.9 and retargeted the Engine and Rules projects plus the PowerShell 7 build selection to .NET 10.0, while retaining the net462 and netstandard2.0 targets. Changes are in 4b51b00; the full solution builds in Debug and Release. |
Co-authored-by: bergmeister <9250262+bergmeister@users.noreply.github.com>
|
Copilot it seems CI is still using PowerShell 7.6.6 so please lower minimum version from 7.6.9 to 7.6.6 |
Co-authored-by: bergmeister <9250262+bergmeister@users.noreply.github.com>
Lowered the loader minimum to PowerShell 7.6.6 in commit |

.NET 8 approaches end of support in November 2026. Move the build and development environment to .NET 10 while preserving the existing runtime targets. Similarly the PowerShell version 7.4 and 7.5 (that uses .NET 8 and 9, respectively) go out of support so increasing minimum PowerShell version support to 7.6. It had to be 7.6.6 and not 7.6.9 because CI runners still use 7.6.6, this can be updated later closer to release time.
global.jsonto .NET SDK10.0.401, retaining feature-band roll-forward.{ "sdk": { "version": "10.0.401", "rollForward": "latestFeature" } }