Despite my initial request for text-based tutorials rather than video tutorials, I've actually spent quite a number of hours watching and/or following along with WPF/MVVM tutorial videos. My most recent find is a decent set of video tutorials by Tosker
Here's one of his playlists that go over the basics, including MVVM: C# WPF Tutorials for Beginners
(Unfortunately, his early videos suffer from very low volume, which I worked around by downloading the videos, pulling out the audio, increasing its volume, then re-saving the videos with the louder audio. Many thanks to 4wd for instructions on how to accomplish this
But despite my many hours of exposure to seeing it in action, I can't help but keep asking myself, "Why use MVVM?" I admit that I don't fully understand how to properly use MVVM since there's so much new to me in all this, including XAML, WPF, and the MVVM pattern itself. But from what I've gleaned, using MVVM just seems like a ton of extra boilerplate and duplicate code, making even trivial things tedious and time consuming.
So I searched the internet and found that I'm far from the first person with the same question.https://stackoverflo...653096/why-use-mvvm/
And the top answer
to that question is really great. Both in explaining that, for trivial cases, using MVVM (or any design pattern) is unnecessary and only adds complication, and also in explaining what benefits MVVM might have on a project over the course of its lifetime.
And of course, along the way I also found more responses talking about "the Jason Dolinger MVVM video," which is something I came across early on in my searches for information but for one reason or another (probably the length) ended up putting off watching until now. So now I'm working on the Jason Dolinger video, trying to gain a better appreciation for how and why to use MVVM.