Support for .NET 10 in Azure Static Web Apps?

[Parse-Vader]

I was wondering if there is any information or roadmap available regarding support for .NET 10 in Azure Static Web Apps. At the moment, Azure Static Web Apps appears to lag behind the latest .NET releases, which makes it difficult to plan upgrades, especially for Blazor WASM or other projects that aim to stay on supported LTS or current versions.

Could you clarify whether .NET 10 support is planned, if there is any estimated timeline, and whether future .NET versions will be supported closer to their official release dates? This information would be very helpful for teams planning long-term maintenance and upgrade strategies.

Thanks in advance!

[cloudhal]

Yes just published an app which failed because of this. It really needs to support the current supported versions of .NET.

[Parse-Vader]

I got a workaround for it

[Parse-Vader]

name: Deploy Ragently to Azure Static Web Apps

on:
push:
branches:
- main

jobs:
deploy_job:
runs-on: ubuntu-latest
name: Build & Deploy Ragently (Blazor WASM .NET 10)

steps:
  - name: Checkout repository
    uses: actions/checkout@v4

  - name: Setup .NET 10
    uses: actions/setup-dotnet@v4
    with:
      dotnet-version: '10.0.x'

  - name: Publish Blazor WebAssembly
    run: |
      dotnet publish Ragently.csproj -c Release

  - name: Deploy to Azure Static Web App
    uses: Azure/static-web-apps-deploy@v1
    with:
      azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_SALMON_MUSHROOM_0AF64D803 }}
      repo_token: ${{ secrets.GITHUB_TOKEN }}
      action: upload

      # folder that actually contains index.html
      app_location: "bin/Release/net10.0/publish/wwwroot"

      skip_app_build: true
      skip_api_build: true
      production_branch: main

  - name: Deployment Summary
    run: |
      echo "✅ Deployment complete!"

[cloudhal]

Yes got this working, thanks.

[JarFrank]

It’s been three months since .NET 10 was released, yet Azure Static Web Apps still does not support it for managed APIs — Oryx fails the build when targeting net10.0. This blocks real-world adoption of .NET 10 for anyone using the built-in /api Functions experience, forcing us to downgrade frameworks or host APIs separately.

Can the team please share a status update or ETA for .NET 10 support in SWA, and clarify whether this will be supported in the near future?

[scottrudy]

Going to attempt to bump this as it's now four months since the release of .NET 10 and eight months before .NET 8 and .NET 9 become officially unsupported by Microsoft. The SWA tooling is actively preventing managed API publishing from GitHub Actions despite all other tooling being ready. See issue #1692 (comment) for more information.

[geoffbrooksnovus]

Asking this questions again - Is there going to be support for .net10 for Blazor SWAs? I have built a series of them for a customer and need to know if there is a future in this tech selection!