Disposing View Models - WPF MVVM NAVIGATION TUTORIAL #6

Показать описание

Learn how and why to dispose view models in a WPF application. This is crucial for preventing memory leaks from view models never getting garbage collected. I also explain why it is preferable to make view model lifetimes transient rather than singleton.

Navigation is an essential piece of an application. In this series, I demonstrate how to implement various navigation scenarios in a WPF MVVM application.

TIMESTAMPS:
0:00 - Introduction
0:22 - Setting Up Disposal Scenario
3:25 - Memory Leak Investigation
4:17 - Implementing Dispose
5:40 - Propagating Disposals
6:37 - Disposing the NavigationBarViewModel
8:18 - Making View Models Transient
11:04 - Conclusion

OTHER LINKS:

Рекомендации по теме

Комментарии

A great video Sean. I've overlooked this issue in the past but now I'm working on larger applications I'll definitely be working this technique into my projects.

tpbarratt

Awesome and nice work.... When you include the Navigation in your MVVM Essentials will be great..

elkhayyat

Thanks for great course! I have question, why destructor is called for LayoutViewModel but it is not called for AccountViewModel or HomeViewModel

viktoryakushenko

I don't hit the destructor sometimes when I go to home... or does the garbage collector not disposing it the moment I hit the home button (like... does it take time for the garbage collector to dispose the AccountViewModel?)

zerosandones

Question: why do you declare events with Action instead of EventHandler? Is it just for the simpler parameters on the handler?

jackkendall

Views are garbage collected but viewmodels must be explicitly disposed. Set all fields and events to null (especially PropertyChanged) because hidden view objects that retain mystery bindings will be your biggest source of memory leaks. And viewmodels will be hard to manage unless you give them a parent-child relationship just like the visual and logical trees. Destructors don't come into play with viewmodels because viewmodels should only be used and disposed on the Dispatcher they were created from.

Disposing View Models - WPF MVVM NAVIGATION TUTORIAL #6

Disposing View Models - WPF MVVM NAVIGATION TUTORIAL #6

Disposing View Models - FULL STACK WPF (.NET CORE) MVVM #31

Disposing view models full stack wpf net core mvvm 31

View Model Communication/Messaging - EASY WPF (.NET 5)

View Models - WPF MVVM TUTORIAL #3

Renavigating w/ a NavigationService - WPF MVVM NAVIGATION TUTORIAL #2

Reusing Commands & Implementing the Sell View/ViewModel - FULL STACK WPF (.NET CORE) MVVM #27

Navigating Between Views - FULL STACK WPF (.NET CORE) MVVM #16

Toggling Form Submission - FULL STACK WPF (.NET CORE) MVVM #32

How to handle WPF control focus with MVVM in C#

Why Does a WPF ComboBox Lose Its SelectedItem When Switching Tabs With Class Items?

WPF Switching Views With Navigation Using MVVM with Prism 8 region

Modals / Popups - WPF MVVM NAVIGATION TUTORIAL #7

Passing Parameters - WPF MVVM NAVIGATION TUTORIAL #3

C# : MVVM - PropertyChanged in Model or ViewModel?

Stores - WPF MVVM TUTORIAL #7

Adding New Views - WPF MVVM NAVIGATION TUTORIAL #9

How much does the Windows Community MVVM Toolkit REALLY help us?

Multiple ViewModel(1)

Using HttpClient Best Practices - FULL STACK WPF (.NET CORE) MVVM #29

Grid Shared Size Scoping/Grouping - EASY WPF (.NET 5)

Class vs. Callback Commands - EASY WPF (.NET 5)

C# Tutorial - Getting Started with Model View View-Model (MVVM) | FoxLearn

C# : this.Dispose() doesn't release memory used by Form after closing it.