Best way to iterate on XAML UI without rebuilding?
Posted: 07 Oct 2026, 05:53
Hi everyone,
I’m new to NoesisGUI and have been experimenting with a small UI using XAML. One thing I’m wondering about is the best workflow for making frequent layout and styling changes.
At the moment, I’m rebuilding and restarting the application whenever I change the XAML, which gets a little slow when I’m tweaking things like margins, fonts, templates and animations.
Is there a recommended way to use the XAML hot-reload workflow during development? I’m particularly interested in whether changes can be previewed directly while the application is running, and if there are any limitations compared with doing a full rebuild.
Any tips from people who use NoesisGUI regularly would be appreciated. Thanks!
I’m new to NoesisGUI and have been experimenting with a small UI using XAML. One thing I’m wondering about is the best workflow for making frequent layout and styling changes.
At the moment, I’m rebuilding and restarting the application whenever I change the XAML, which gets a little slow when I’m tweaking things like margins, fonts, templates and animations.
Is there a recommended way to use the XAML hot-reload workflow during development? I’m particularly interested in whether changes can be previewed directly while the application is running, and if there are any limitations compared with doing a full rebuild.
Any tips from people who use NoesisGUI regularly would be appreciated. Thanks!