Skip to content

Target PowerShell host to .NET 10#53

Open
eosfor wants to merge 2 commits into
DataficationSDK:mainfrom
eosfor:pr/powershell-net10
Open

Target PowerShell host to .NET 10#53
eosfor wants to merge 2 commits into
DataficationSDK:mainfrom
eosfor:pr/powershell-net10

Conversation

@eosfor
Copy link
Copy Markdown
Contributor

@eosfor eosfor commented May 16, 2026

Summary

Follow-up after #48.

Moves the local/F5 Verso host path to .NET 10 while keeping the Verso.PowerShell package compatible with both runtime lines.

Changes

  • Target Verso.Host and Verso.Host.Tests to net10.0.
  • Multi-target Verso.PowerShell for net8.0 and net10.0.
  • Use TFM-specific PowerShell SDK versions:
    • net8.0 -> Microsoft.PowerShell.SDK 7.4.15
    • net10.0 -> Microsoft.PowerShell.SDK 7.6.1
  • Use TFM-specific Roslyn versions to avoid dependency conflicts with PowerShell SDK 7.6.x.
  • Publish the VS Code bundled host explicitly with -f net10.0.
  • Prefer net10 host discovery in VS Code development mode, with net8 fallback.

Base

#48 is merged. This branch has been rebuilt on current main, so the PR now contains only the .NET 10 follow-up changes.

Validation

  • dotnet test tests/Verso.PowerShell.Tests/Verso.PowerShell.Tests.csproj -c Debug --no-restore
  • dotnet test tests/Verso.Host.Tests/Verso.Host.Tests.csproj -c Debug --no-restore
  • npm run lint
  • npm run pretest

@eosfor eosfor force-pushed the pr/powershell-net10 branch from b1b2e58 to 69ae7d7 Compare May 18, 2026 05:30
@eosfor eosfor marked this pull request as ready for review May 18, 2026 05:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant