chore: Update all samples to use the latest TFMs

[jamescrosswell]

Resolves #4584

• Update all samples to use the latest TFM #4584

---

#skip-changelog

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.85%. Comparing base (09a72cb) to head (6412515).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4782      +/-   ##
==========================================
- Coverage   73.87%   73.85%   -0.02%     
==========================================
  Files         483      483              
  Lines       17578    17578              
  Branches     3464     3464              
==========================================
- Hits        12985    12983       -2     
- Misses       3740     3741       +1     
- Partials      853      854       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jamescrosswell]

The error we're seeing now in CI is:

/usr/share/dotnet/packs/Microsoft.NET.Runtime.WebAssembly.Sdk/10.0.0/Sdk/WasmApp.Common.targets(853,5): error : /usr/share/dotnet/packs/Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-arm64/10.0.0/tools/bin/clang: line 25: /usr/share/dotnet/packs/Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-arm64/10.0.0/tools/bin/clang-19: not found [took 0.65s] [/__w/sentry-dotnet/sentry-dotnet/samples/Sentry.Samples.AspNetCore.Blazor.Wasm/Sentry.Samples.AspNetCore.Blazor.Wasm.csproj]

This may be related to:

• Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-x64 version 10.0.0 contains clang-19 linked against libc dotnet/runtime#121975

@Flash0ver potentially we revert to net9 for the WASM sample until this is a bit more stable in .net 10?

[jamescrosswell]

Inexplicably, this commit seems to have broken the unit tests on linux-musl-x64. They don't fail... they just never complete and we can't get at the logs to work out why. 😞

Possibly the commit is entirely unrelated but, if so, I can't see any other differences between the environments between the successful and unsuccessful runs.

Commit 6722643 confirms it's nothing to do with the change, but we do finally get some clues from the logs:

Error: System.IO.IOException : No space left on device : '/tmp/1d608ce7-dee1-427a-8947-daac2bd3a2b1'

[cursor]

Bug: Missing @ prefix in Razor attribute expression

The NotFoundPage attribute value is missing the @ prefix for the C# expression. The value typeof(Pages.NotFound) is being treated as a string literal instead of a type expression. Compare with AppAssembly="@typeof(App).Assembly" and DefaultLayout="@typeof(MainLayout)" on the same component which correctly use the @ prefix. This will cause the Router to not properly recognize the NotFound page type.

 

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

This PR will not appear in the changelog.

---

_{🤖 This preview updates automatically when you update the PR.}