Fix Windows build-server platform mismatch in CI

[Copilot]

The failing GitHub Actions run was isolated to the Windows build-server job. MSBuild was invoked with a platform name that does not exist in the legacy ResizingServer.csproj, causing the standalone project build to fail before packaging.

• Root cause

  • The workflow passed /p:Platform="Any CPU" while ResizingServer.csproj defines its configurations as Debug|AnyCPU and Release|AnyCPU.

• Change

  • Updated the Windows build-server workflow step to build ResizingServer.csproj with the platform name MSBuild can resolve for this project:

    - name: Build ResizingServer
      run: msbuild source/ResizingServer/ResizingServer.csproj /p:Configuration=Release /p:Platform=AnyCPU

• Effect

  • Keeps the existing workflow structure intact.
  • Restores compatibility for direct CI builds of the legacy .NET Framework web project on Windows runners.

[Copilot]

🟢 Approval recommended

The workflow now uses the project’s valid AnyCPU platform configuration.

Pull request overview

Fixes the Windows CI build-server platform mismatch for the legacy ResizingServer project.

Changes:

• Changed the MSBuild platform from Any CPU to AnyCPU.

File summaries

File	Description
.github/workflows/dotnet-ci-release.yml	Corrects the Windows server build platform argument.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.