Hey, if you're strictly adhering to MVVM architecture, is it better to instantiate/show windows in the code-behind, or in the ViewModel? From what I understand, putting view-related logic in the ViewModel is a violation of the MVVM pattern, but there's a lot of conflicting answers to this online. Also, congrats on the great tutorial.
Thanks! Lots of conflicting answers on this one is the truth -- this is a very touchy subject with a lot of people. My opinion (take it with a grain of salt) is if you are strictly adhering to it, then you should not, but instead use something like a window service interface/dependency injection to achieve full separation. Further opinion (more grains of salt): I rarely advise projects to adhere extremely strictly unless the project is massive/lots of moving parts (easier on maintenance), or uses a large varied or inexperienced team (easier on peer review/prevents laziness). As long as you succeed in the separation of concerns in both dev and test - it is very beneficial. Strict rules (like zero code behind) generally just slow down development and introduce unnecessary complexity. Hope this helps.
That was a wonderful video. You helped me a lot. Can you teach how to create some mvc model? To change main windows with a controller? using a 'panel' or directly in the 'grids'. ❤
Thank you, I'm glad it helped! In just a few videos i will be starting a set of videos on MVVM. It's extremely close to MVC, except it uses a "view model" as a controller, and fits really well with WPF.
I would really like to do this, but at the moment I don't have the time. Currently work is keeping me so busy that I'm a bit behind on creating the videos themselves, but maybe once things calm down I can do something like this. Thank you for the suggestion, and for watching!
Name is a property on a class in .NET. x:Name is a XAML-specific attribute that all elements can have. Functionally, they are basically the same thing. I generally only use x:Name when Name isn't available, but that's just me.
