Upgrade PSCommander to .NET 10

.github/workflows/ci.yml

@@ -22,10 +22,10 @@ jobs:
       with:
         fetch-depth: 0
 
-    - name: Install .NET Core
-      uses: actions/setup-dotnet@v3
+    - name: Install .NET
+      uses: actions/setup-dotnet@v4
       with:
-        dotnet-version: 6.0.x
+        dotnet-version: 10.0.x
 
     - name: Build
-      run: dotnet publish
+      run: dotnet publish .\PSCommander.slnx

.github/workflows/production.yml

@@ -19,16 +19,16 @@ jobs:
       with:
         fetch-depth: 0
 
-    - name: Install .NET Core
-      uses: actions/setup-dotnet@v3
+    - name: Install .NET
+      uses: actions/setup-dotnet@v4
       with:
-        dotnet-version: 6.0.x
+        dotnet-version: 10.0.x
 
     - name: Build
-      run: dotnet publish -o pscommander
+      run: dotnet publish .\pscommander\pscommander.csproj -o pscommander
 
     - name: Release
       run: Publish-Module -Path .\pscommander -NuGetApiKey $Env:APIKEY
       env:
         APIKEY: ${{ secrets.IMS_PSGALLERY }}
-      shell: pwsh
+      shell: pwsh

AGENTS.md

@@ -13,7 +13,7 @@ The solution has two projects:
 
 ## Important files and directories
 
-- `PSCommander.sln`: solution entry point.
+- `PSCommander.slnx`: solution entry point.
 - `pscommander\PSCommander.psm1`: public PowerShell cmdlet functions such as `New-CommanderHotKey`, `New-CommanderSchedule`, `Start-Commander`, and `Register-CommanderDataSource`.
 - `pscommander\PSCommander.psd1`: PowerShell module manifest.
 - `pscommander\App.xaml.cs`: command-line argument parsing. Secondary invocations forward file association, shortcut, context menu, and protocol commands over named pipes.
@@ -28,7 +28,7 @@ The solution has two projects:
 Run commands from the repository root unless noted.
 
 ```powershell
-dotnet restore .\PSCommander.sln
+dotnet restore .\PSCommander.slnx
 dotnet publish
 ```
 
@@ -41,7 +41,7 @@ dotnet publish .\pscommander\pscommander.csproj
 dotnet build .\pscommander.models\pscommander.models.csproj
 ```
 
-This is a Windows-only WPF app (`net6.0-windows`, `UseWPF`, `UseWindowsForms`). Do not assume Linux/macOS validation will work.
+This is a Windows-only WPF app (`net10.0-windows`, `UseWPF`, `UseWindowsForms`). Do not assume Linux/macOS validation will work.
 
 ## Runtime behavior to preserve
 

PSCommander.slnx

@@ -0,0 +1,4 @@
+<Solution>
+  <Project Path="pscommander.models/pscommander.models.csproj" />
+  <Project Path="pscommander/pscommander.csproj" />
+</Solution>

global.json

@@ -0,0 +1,7 @@
+{
+  "sdk": {
+    "version": "10.0.100",
+    "rollForward": "latestFeature",
+    "allowPrerelease": false
+  }
+}

pscommander/pscommander.csproj

@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <OutputType>WinExe</OutputType>
-    <TargetFramework>net6.0-windows</TargetFramework>
+    <TargetFramework>net10.0-windows</TargetFramework>
     <UseWPF>true</UseWPF>
     <UseWindowsForms>true</UseWindowsForms>
     <ApplicationIcon>Resources\icon.ico</ApplicationIcon>
@@ -16,8 +16,8 @@
     <PackageReference Include="LiveCharts.Wpf" Version="0.9.7" />
     <PackageReference Include="MaterialDesignColors" Version="2.0.0" />
     <PackageReference Include="MaterialDesignThemes" Version="4.0.0" />
-    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.1.3" />
-    <PackageReference Include="Newtonsoft.Json" Version="12.0.3" />
+    <PackageReference Include="Microsoft.PowerShell.SDK" Version="7.6.4" />
+    <PackageReference Include="Newtonsoft.Json" Version="13.0.4" />
   </ItemGroup>
 
   <ItemGroup>
@@ -37,4 +37,4 @@
     <Resource Include="Resources\icon.ico" />
   </ItemGroup>
 
-</Project>
+</Project>