Uploaded March 2025 | Updated September 2026, 2 weeks ago

---

In this spring-themed Episode 71 of The Blazor Puzzle, Carl Franklin (AppvNext) and Jeff Fritz (Microsoft) dive into a common developer challenge: how do you track dirty fields in a large Blazor app without modifying your models?

💡 Instead of rewriting every getter and setter across 50+ models, they show you a clever UI-only solution using event handlers and a simple dictionary to detect changes. Plus, they explore real-world use cases like autosave, user auditing, and canceling navigation on unsaved changes.

🔹 Topics Covered:
✔️ Dirty flag detection in Blazor without modifying models
✔️ How to track property changes using @oninput
✔️ Saving modified fields with a dictionary
✔️ Preventing navigation with unsaved changes
✔️ Making a custom Blazor input component for reusability
✔️ Why Blazor makes this way easier than JavaScript

💬 Have a Blazor coding puzzle of your own? Send it to blazorpuzzle@appvnext.com — you might even get a mug!

🔗 Resources & Code:
Check out the full GitHub repository with test code and solutions here:

📌 Want to level up your Blazor testing skills? Subscribe & join the puzzle! 🧩

Get Started Today – Free 30 Day Trial
dxpr.es/NUGET
dxpr.es/FREE-TRIAL

Pricing and Online Demos
dxpr.es/BUY
dxpr.es/DEMOS

We Are Here to Help
dxpr.es/SUPPORT

Follow DevExpress on Social Media
dxpr.es/FACEBOOK
dxpr.es/TWITTER
dxpr.es/BLOGS

Review Customer Testimonials
dxpr.es/TESTIMONIALS
dxpr.es/MARKETPLACE

#DevExpress, #devexpress_blazor #blazor #microsoft #carlfranklin #Jefffritz #Blazor #Blazor #Playwright #AutomationTesting #CSharp #DotNet #DirtyFlag #ASPNetCore #BlazorPuzzle #AIinDev