Skip to content

chore: upgrade BMM.Web to .NET 10 - #672

Merged
KillerX merged 1 commit into
mainfrom
chore/dotnet-10
Nov 2, 2026
Merged

KillerX merged 1 commit into
mainfrom
chore/dotnet-10

Conversation

@KillerX

@KillerX KillerX commented Nov 2, 2026

Copy link
Copy Markdown
Member

Why

prod-bmm-web was switched to the .NET 10 runtime stack and now fails to start:
ContainerStartupFailure: Container exited with exit code 150.

Exit code 150 (0x96) is hostfxr's "framework not found". The app targets net7.0, and the .NET 10 Linux image only ships the 10.0 shared framework.

Changes

  • BMM.Web/BMM.Web.csproj: net7.0 → net10.0
  • build-and-deploy.yml: actions/setup-dotnet@v1 with 7.x → @v4 with 10.0.x

Testing

  • Not built locally. The identical host code in BMM-Website builds cleanly on .NET 10 (nullable warnings only).
  • CI on this PR builds the .NET project. After merge, check that prod-bmm-web shows the instance as Running and serves / and a /track/<id> link preview.

🤖 Generated with Claude Code

The prod-bmm-web App Service runtime was switched to .NET 10, but the app
still targeted net7.0, so the container exited with code 150 (framework
not found). Retarget to net10.0 and install the .NET 10 SDK in CI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@KillerX
KillerX merged commit a9a81a6 into main Nov 2, 2026
7 of 9 checks passed
@KillerX
KillerX deleted the chore/dotnet-10 branch November 2, 2026 10:23

This branch was successfully deployed

1 active deployment
prod — 9f35a36f Deployed Nov 2, 2026 by KillerX via Remove Azure Static Web App #2640
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