[Andrea-Bruno]

Summary

Upgrades the whole solution from .NET 9 to .NET 10:

• Retarget all 40 projects from net9.0 to net10.0
• Microsoft.AspNetCore / Microsoft.Extensions / runtime packages bumped to 10.0.11
• Aspire stack: Aspire.AppHost.Sdk and Aspire.Hosting.AppHost → 13.5.3, Microsoft.Extensions.Http.Resilience / Microsoft.Extensions.ServiceDiscovery → 10.9.0
• Serilog extensions aligned to the 10.x line (Serilog core → 4.3.0)
• Pomelo (MySQL): 9.0.0-preview.2.efcore.9.0.0 → 9.0.0 stable; DM (DaMeng): 8.0.0.33671 → 9.0.0.43760
• Docker base images → aspnet/sdk:10.0; install-service.bat, build scripts and docs updated

Note on EF Core

EF Core intentionally stays on 9.0.x: the Pomelo (MySQL) and DM (DaMeng) providers do not support EF Core 10 yet (Pomelo 9.0.0 restricts Microsoft.EntityFrameworkCore.Relational to <= 9.0.999). Once those vendors release EF Core 10 support, the whole EF Core stack can be moved to 10.x.

Verification

• dotnet build Thor.sln -c Release on SDK 10.0.400 → 0 errors
• The solution contains no test projects
• Local restore used api.nuget.org as source (the nuget.cdn.azure.cn mirror was unreachable from this network)

[github-actions]

Message that will be displayed on users' first pull request

[Andrea-Bruno]

We opened issue #88 to note that this pull request is blocked by a failing "label" check caused by a missing .github/labeler.yml in the repository. This is outside our control and stops the pull request from completing.

[Andrea-Bruno]

The failing label check is not caused by this change. It fails because the workflow points at .github/labeler.yml, which does not exist in this repository, so the labeler action returns Not Found. That is a repository configuration gap and is already reported in issue #88. Our change here is only the .NET 10 upgrade and does not touch the labeler setup. Once a maintainer adds the missing labeler.yml, or drops the step, this check will pass.