Live Q&A – Scott Hunter
summary
A live Q&A details that hot reload exists as both a temporary unsaved-change button (which may be removed) and a save-to-trigger file-watcher, and it patches compiled C# including event handlers across WinForms, WPF, Console, ASP.NET, Blazor and MAUI. Blazor in .NET 6 gains AOT vs JIT WebAssembly compilation for much faster startup at the cost of larger binaries; ready-to-run gives a middle ground. Minimal APIs or startup code that already executed still require a restart (team prototypes faster restarts), Unity modernisation is ~1–1.5 years out, and iOS device testing from Windows works but publishing needs a Mac.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:51Ahead of Time Compilation
- 8:09Blazer
- 11:37Ready To Run
- 15:15Ios Apps in Visual Studio
- 16:22Is There any Advice That We Can Do Ahead of Time To Write Code so that It's Better Available for Hot Reload
related talks
01h 01mWhat’s next for Blazor, and .NET on WASI
06h 43mVisual Studio for Mac: Refresh();
01h 09mBlazor Wasm Hot Reload Explained: Real-Time Dev with Rider
47mWhat's new in .NET 8 for Web frontends backends and futures?
46mASP.NET Core and Blazor futures Q&A
01h 03mQ&A – Ask the #dotNET team
47mBlazor
07h 34mC#, F#, Blazor Wasm Hot Reload, Contract Testing, and More (Day 2)