C# WPF Tutorial #23 - Using ViewModels in MVVM

[@mumk]

The sound quality of this tutorial was lit 🔥

[@gayatrik9084]

Thank you for being so generous with your time and sharing your knowledge

[@pierrestcergues]

Your tutorials are a pure gift! thanks!

[@KampaPlays]

Thank you!!

[@coldwolf5050]

As someone also coming from asking GPT, this video nails it. Nicely done!

[@wookyumkim4669]

Finally!! I have reached to this video! 🤣🤣 I'm so glad that you are presenting this mvvm concept with datagrid example. 😊😊 Thank you so much Kampa! 😄😄

[@KampaPlays]

Finally made it here! :)

[@אלוןאדר]

Great tutorial. I learned new features on WPF. Thanks.

[@KampaPlays]

Awesome, thank you!

[@robinheyer708]

It's almost disappointing how straightforward this is after getting worked up about "the unknown" :P

[@KampaPlays]

🤣Yes!! So many times our worst enemy in programming is over-engineering and over-complication!

[@בןמשה-ט3ע]

bro , with all the questions ive asked chat gpt about this , this video is more comprihensive and more comprihesible.. mabe they wont replace us afterall. greaeat video man

[@PhilipHenningD]

Thank you for these videos!! I've generally been watching them once through and then playing back as I code along.. however this video is going to take a few re-watches I think. I must admit that I am already a little bit confused as to why you are entering the list data in the ViewModel and not the Model? Am I barking up the wrong tree if I assume that it's something to do with us not hooking into an external data source? Apologies in advance if you have covered this in the next video 🙂 Many thanks again, Phil

[@rahulgoutham7102]

Very well explained. Thanks a ton.

[@KampaPlays]

Awesome! Glad to help.

[@volkangundogdu1008]

Thanks!

[@KampaPlays]

Thanks so much, really appreciate that!!!

[@Stars.Stripes.andVan]

Great video as usual! I didn't know that we don't have to implement INotifyPropertyChanged for ObservableCollection Lol. Thanks for making me realize that my knowledge of WPF is still very limited.😆

[@KampaPlays]

I understand that, it's a great framework, but its not always 100% intuitive! 😂

[@artemky3bmu45]

Thank you for your lessons

[@thomasaminer]

Thank you, a perfect video!

[@kushaljain-m5e]

Nice easy to understands

[@thushanshanilka3251]

Great tutorial series. Only problem is having to wait too long for the next video.

[@KampaPlays]

Thanks so much! Maybe one day I'll have time to up the release tempo!

[@semautomacao991]

Start with a tip😋

[@The1Wolfcast]

Can't believe I struggled with understand MVVM in the past. I am more confused how every video in this playlist worked without error every time??!?!

[@mythmaker6155]

Great tutorial. i finished all the video from playlist. can tell how many video left? and when you are going to upload again?

[@KampaPlays]

Thank you and thanks for watching! I'm not exactly sure, maybe 5-10? I'm trying to release 1 per week, but work is very busy right now, so occasionally I fall behind. Should be another coming out this week though.

[@윤태웅-i7n]

Thank you for the video!

[@JuvilleBeats]

I think I understand the basic structure of MVVM but one thing bugs me for a long time and that's the fact that one still has to refer to the objects and propertiers but in this case through the bindings. What's the point of that? How is the UI decoupled from the Code in that case? How can a designer make the UI without knowing how the objects and properties are named? I understand that both are separately testable but that's all? Any hints and tipps from anyone are greatly appreciated!

[@vitalijgrabovan2061]

Hello Kampa, as always the best video about WPF that I have seen so far - and I have seen them alot !!! Any idea why intellisense is not recommending properties in the selection list when you are typing them in the XAML window ? I saw in some videos tha other people dont have this problem. I tired everything and cant get it working. Thx

[@KampaPlays]

Thanks so much! Sometimes the XAML designer gets hosed up for some reason - I have noticed this at times. Usually a clean/build or a VS restart will fix it. It also could not be giving you specific properties due to namespace/includes not being listed correctly or built. I hope it works for you!

[@kojhkimo]

Amazing!!

[@KampaPlays]

Thanks so much!

[@dakloafitz6347]

Uhh nice!! MVVM!! love it :D I just startet playing around with MVVM a few days ago. The only part i´m not getting is, how do i get data from one viewmodel to the other? So lets say the first view is the inventory view like you´ve just drawn, the second one is e.g. a details view for one specific item. So i need the have access to the same ObservableCollection as in the first view. Hope you´ll get to that soon :) Thanks for ur videos, they have helped me a lot :)

[@KampaPlays]

Thanks! So one easy way to do what you are asking is to create the second viewmodel in the first wherever you are opening your new window, and pass it to the new window itself. Something like: ViewModel1: void ShowDetails() vm2 = new DetailsVM(); view2 = new DetailsView(vm2) This way you can flow data (or references to data) down to your children/subcomponents from where they originate. Things stay encapsulated nicely this way rather than using globals or some other static method to pass the data around.

[@priyankaabbineni4231]

Pls do a video on treeview control in MVVm

[@KampaPlays]

Added it to my list.

[@reyaadelkomy8046]

Really create a tutorial and create job.

[@dariostromajer1625]

new video when??

[@KampaPlays]

Maybe about 10 minutes? 😁

[@dariostromajer1625]

@@KampaPlays hell yeahh!!