WPF hot reload builds on C# hot reload model
Jump to 0:04The new WPF hot reload capability extends a pattern developers already know. The same edit-and-save workflow that applies to C# code now works for XAML markup and UI changes.
JetBrains' IDE now lets developers modify WPF applications without rebuilding, speeding up the edit-test cycle.
Want the next one from this channel too?
The new WPF hot reload capability extends a pattern developers already know. The same edit-and-save workflow that applies to C# code now works for XAML markup and UI changes.
WPF hot reload lets developers modify XAML in Rider and see the changes while the application is running. When a file is saved with Ctrl+S, changes apply automatically to the live application without rebuilding. Text, buttons, and other UI elements update in real time. The Windows application window reflects changes instantly, keeping the running state intact.
Pasting a XAML snippet into the editor and saving triggers an immediate update in the running application. A StackPanel containing text and a button was added through a code snippet and appeared in the application window without any rebuild or restart. The live application updated automatically to include both the text element and the button, visible on the Windows application in real time.
Style properties like font size can be modified and take effect immediately in the running application. Increasing the font size of text makes it more readable without requiring a restart or rebuild.
WPF hot reload is not limited to visual properties. Developers can add click handlers to XAML elements and modify the underlying application logic and behavior. Method auto-completion is available for event handlers, making it easy to wire up new interactions. Logic changes are applied alongside markup changes, so both the UI structure and its behavior can evolve without stopping the application.
The hot reload feature operates alongside new .NET 10 message box options, which expand the result handling available for dialog boxes. This allows developers to use modern .NET features while benefiting from live code changes.
Breakpoints set in newly added code paths remain active during WPF hot reload. After using the C# hot reload button to apply changes, the debugger becomes active when the modified code is triggered. This allows developers to step through the execution, inspect variables, and control the program flow without restarting the application. The breakpoint becomes functional once the hot reload is applied, enabling immediate debugging of new event handlers and logic.
After hot reload applies code changes, saving the XAML file with Ctrl+S activates newly added event handlers. A button click event was added via hot reload and immediately became responsive, triggering a .NET 10 message box without requiring an application restart. When the message box button (such as Retry) was clicked, it triggered the previously set breakpoint, allowing the developer to inspect the application state.
WPF hot reload is available in Rider 2026.2 as part of the dotUltimate suite.
Answers come from the transcript, with the exact spot cited.
Want the next one from this channel too?
When JetBrains publishes, we'll write it up like the one you just read and email it to you.
{channel} published 6 in the last 7 days.
We skip Shorts. You can unfollow any time.
JetBrains DataGrip Introduces AI Agents for Enhanced Database Management and AnalysisJetBrainsyesterday · 13:17 · 57 views · Created yesterday
Go 1.27 Introduces Generic Methods, JSON v2, and Tooling Enhancements Amidst AI Era DiscussionsJetBrainsyesterday · 1:14:40 · 3.2K views · Created yesterday
JetBrains Rider Introduces Drag-and-Drop for Godot Scene PreviewJetBrains2 days ago · 1:38 · 56 views · Created 2 days ago