Are you implementing INotifyPropertyChanged again? Are using INotifyPropertyChanged on your UI control instead of a DependencyProperty? Stop! In this video we'll explain the difference between these two different patterns and when to use each one. We'll cover how to use the MVVM Toolkit (part of the .NET Community Toolkit) to do all the hard work for you and remove the boilerplate for your ViewModels, and then how to use the new DependencyProperty source generator from Windows Community Toolkit Labs when working with UI controls in XAML.
 
Project Source Code and MVVM Architecture project: 
https://github.com/michael-hawker/MVVMNetConfApp

MVVM Architecture Video:
https://youtu.be/83UVWrfYreU

XAML Architecture Video:
https://youtu.be/AM7Txg78Y7E

MVVM Toolkit App:
http://aka.ms/mvvmtoolkitapp

Windows Community Toolkit Labs
https://aka.ms/toolkit/labs/windows
 
🪟 Learn more about building for Windows
https://aka.ms/wdyt/wdc
 
📃 Check out our Windows Developer Blog
https://aka.ms/wdyt/blog
 
🔨 Learn more about building on Windows
https://aka.ms/wdyt/buildon
 
#windows #xaml #winui #mvvm

Windows Developer

The post discusses the differences between using INotifyPropertyChanged and dependency properties in application development, particularly in .NET frameworks like WPF and WinUI. It emphasizes the usage of the MVVM toolkit for streamlined development, reducing the need to manually implement property change notifications. Dependency properties are highlighted as essential for effective data binding in XAML-based applications. Source generators are presented as a solution to eliminate boilerplate code, enhancing development efficiency.

INotifyPropertyChanged vs DependencyProperty Which Is Better?