Updating our Blazor site to .NET 10 Part 5! - Deep breaths (pun intended)

We’re back after Virtual .NET Conf and immediately slide into classic *Coding After Work*: snacks, temperature debates, stray cats, raccoons, and zero planning.

On the coding side, they finishes a .NET 10 migration, updates all the things, deals with vulnerability warnings, pokes at MCP in Visual Studio… and then spends most of the episode chasing down a CSS issue.
An issue Jimmy has solved before.
Explained before.
Helped countless other people with before.
On stream. In talks. In videos.

Yes — CSS isolation.
Yes — `::deep`.
Yes — it was that.

Which honestly makes it extra relatable: knowing the answer doesn’t stop you from forgetting it when it’s *your own* code. We eventually fix the UI, talk about why `StateHasChanged` can hurt performance, improve state persistence between Server and WASM, and end with a fresh bug as a perfect cliffhanger for next time.
An error has occurred. This application may no longer respond until reloaded. Reload 🗙