STOP Modifying WPF Controls Directly! - View Model Refactoring For MVVM

Rule number 1 about WPF club: We don't talk about WPF club.

Wait! That's not right -- Rule number 1 is about directly manipulating our views!

In WPF, the predominant way of designing user interfaces is leveraging MVVM. We use binding to get our controls (the views) hooked up to the state of the view models.

Through data-binding, when our view models update, the views are triggered to get updates for the new state! This works the other way too, of course.

In this video tutorial, we'll refactor a splash screen with a progress bar to support a view model. We'll avoid updating the controls on the view directly and leverage data-binding!

----
🔑 Membership & Subscriptions:

🧠 Courses:

🗣️ Social Media & Links:

❤️ Affiliations & Products/Services That I Love:
----

#dotnet #csharp #wpf #frontend

[DevLeader]

💡 Learn how to program in C#:
🧠Deep dive on C#:
🎁Zero to Hero C# Bundle:
💪 Skill up your refactoring:
✉ Subscribe to my free software engineering newsletter:

[williamliu]

Thanks! More WPF MVVM things please...

[Kevmoens]

Have you seen prism? They use a view model locator to write up views and view models

[selvakumar.s]

Sir i am recently placed as .net with wpf developer but some of my friends says wpf is not familiar and very less scope in future, what is ur thoughts?