You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 64d5caf
Browse filesBrowse the repository at this point in the historyBrowse files
Retarget the Hosting and Test projects from `net8.0` to `net10.0` (the new
LTS), pin `global.json` to the 10.0.301 SDK, and move
`Microsoft.PowerShell.SDK` from 7.4.14 to 7.6.3 — the PowerShell 7.6 LTS
line that aligns with .NET 10, mirroring how 7.4 aligned with .NET 8.
The .NET 10 SDK ships newer Roslyn analyzers that we enforce as build errors
(`EnforceCodeStyleInBuild`), so a few pre-existing constructs needed cleanup
to stay green:
- `VersionUtils.IsPS74` matched *exactly* 7.4, but the variable-completion
detail it gates was added in 7.4 and persists in 7.6. It now reads
`IsPS74OrGreater` (>= 7.4); without it the `CompletesVariableInFile` test
fails on 7.6.
- Removed the unused `_workspaceService` field and constructor parameter from
`ReferencesCodeLensProvider` — dead since we removed the notion of
referenced files (IDE0052).
- Adopted the C# 14 `field` keyword in `SynchronousTask.Result` and
`ReferenceTable.IsInitialized` (IDE0032), null-conditional assignment in
`PowerShellDebugContext` and `RemoteFileManagerService` (IDE0031), dropped
redundant interface accessibility modifiers (IDE0040), and simplified a
`TextEdit` reference. `LangVersion` is `latest`, which is now C# 14.
I built core (`netstandard2.0`), Hosting, Test, and E2E (all `net10.0`)
clean and confirmed the previously-failing completion test passes on 7.6.3.
Drafted by Copilot (Claude Opus 4.8).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments