WPF MVVM Step by Step ( Windows Presentation Foundation) 

Do not miss our Interview Question video series 30 Important C# Interview Questions : ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-BKynEBPqiIM.html 25 Important ASP.NET Interview Questions : ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-pXmMdmJUC0g.html 25 Angular Interview Questions : ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE--jeoyDJDsSM.html 5 MSBI Interview Questions : ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5E815aXAwYQ.html

Excellent video, good work! This is the first MVVM tutorial I've seen that actually explains why you should use MVVM. It makes it so much easier to understand MVVM when it is desciribed in the context of an evolution from the old 3 tier architecture.

I've been struggling to understand MVVM, but I think I "get it" now. Thank you for such an awesome explanation!

You are a great teacher, the fact you have this put up for free is an even better service to the programming community.

I wished I saw this earlier...your explanation is so helpful for a beginner like me. Thank you sir.

Fantastic video! I really appreciate that you made it as simple as possible while giving enough broad context as to how and why these patterns evolved. Very helpful!

This is the first time i found a comprehensive lesson for MVVM. Thank you so much.

I love watching all QuestPond videos. So useful and explained in very simple language. I highly recommend my friends to watch it for any kind of training. Keep it up. We need you.

Thank you so much. This tutorial is very helpful for beginners like me.

Just came across this today and wish I had found it a lot sooner! Absolutely amazing job explaining this.

Beautifully made tutorial that is simple enough to introduce a complex subject. Thank you so much.

Great video, this video is one of the best explanation of MVVM i have seen - thank you.

I knew I would get all the answers to my questions from Shiv sir. Amazing explanation

Get a pop filter and adjust your gain.

Really nice video.. I could not find next video that was referred (commands in WPF MVVM). Can you please help me out in finding the video? Thanks

I've heard people say that using 3 tier architecture means contained changes but that is often not the case with UI changes. Whenever you make a UI change you almost always have to make a change to the data access layer too.

thank you . it was the best tutorial which presents best way of learning WPF MVVM .i wish you had a such tutorial for bindings and references in WPF.

Very good explanation....for beginners

Thank you! This is the best video about MVVM I've found since days. Finally I got it =)

Extremely helpful, thank you! I liked that everything was step by step with an actual example.

Excellent! You lay out a very clear vision...... please let us know where part II is.

very good video, very good teaching skills. Like the step by step approach, which makes things much clear. Thank you. Keep up your good work.

This is the video, I am looking for since time. Thank you very much

It's really awesome vedio , explained in an easy way to understand... Gr8... I am not able to find other vedios..

Best teacher ever ! Keep up the great work.

Great video. Thanks Sir .I have query, Can we use MVC over MVVM or what is the main difference or Why MVC suites for only web application.

No comment , god bless you.

This was explained very well! Thanks

I wish i could give you more than one like

Extremely easy and well explained video. Thank you!

Thank you, Sir. Your explanation is clearly understandable.

Excellent video! Talented teacher

Excellent Tutorial and Video. Thanks Shiv.

Great tutorial. Really helped me understand MVVM. Thank you!

Great video. Thank you so much. You are amazing "explainer", who is able to communicate concepts, rare talent. Where can I get further course ? I checked questpond, but did not find subscription to WPF video courses.

Great video, great explanation, finally understood the concept, thank-you!

Nice tutorial, but i have a question about this example with C# WPF it's possible to use converters in the binding, so it would be possible to skip this view model and bind the view to the model directly and then add converters to the binding to transform the int to a color, or the string to a bool etc Would this still be considered MVVM in this case if the View is directly bound to the Model properties with binding converter classes?

thank you very much i always liked to know how to use mvvm with wpf

best video on mvvm.

The perfect video tutorial....Great work dude

That's a great vdo.thanks a lot for such a clear 👏 explanation

Well explained, Thank you for all your efforts..

Actual MVVM starts at 18:15. However before that its very informative...

Thank you from Armenia ))

It's very difficult to find the videos you have referenced like the on one data binding. Can you provide links? I haven't been able to find it despite searching your channel.

Very nice and detail explanation. Thanks

Hi I did not find the next video about MVVM, can you please let me knoy?

Sir Can you please post Wpf questions and answers video series link? not able to find out

Finally i can say i understood MVVM

Great explanation. Good job with the tutorials.

the best video i had see , good job you are the best

Very helpful ThankYou! Are the other videos uploaded? I can't find them thanks.

What an amazing lecture!!!

This is a great channel but this video just destroyed my speakers. Please adjust the volume... Thanks

Thank you very much, this video is really helpful

You are amazing, man. Good work

Thank for MVVM explanation. Can we use MVVM in asp.net webforms projects?

Thank you very helpful regarding MVVM :-)

Great explained. Many thanks!

really useful. thanks. going to have to rethink my layout now :D

This was super helpful, thank you!

Such a good video. Thank you.

Really Great and simple !!! Cheers

Amazing video sir! Looking forward to more videos!

Thank you very much for this video, it really helped me!

Simple, yet Excellent!

Great video for understanding MVVM

Well explained! Thank you so much!

Hi, how to display dialog box in ViewModel without referring the UI framework ?

Great vid , i finally understand !

Link for 2nd video ? Cant find it.

Many Thanks for this video...

Nice explanation, Thanks a lot!

Has something changed since you released this? When I add the to seed the data I get an error that the CustViewModel name space is not found.

Very good video for beginner

This video was very helpful. please send link for next video.Thanks

Great video. Thank you so much.

Please upload future scope of MVVM

Mhhh something is not really clear for me. How did you assign the DataContext to the Windows? Usually all the examples that I found, approach this in 2 ways, the first is to create in the behind code a MainWindowsClass and setting its DataContext property. The second is to assign the Window.DataContext directly in the xaml file. In this example you didn't use neither of these method. How can the MainWindows be referenced to the ViewModel?

u are the best

error :- here IsMarried property is not accessible setter

Informative...Thank you

28:40 when I try to bind I get error message that custns does not exist in XML namespace clr-namespace:CustomerViewModel. I followed one to one everything. why am I getting this? I am doing it on VS 2013 version. thanks

Great Job.

Nice video series

you are awesome.

Nice Video

simply awesome +1

LONG TIME SUBSCRIBER FIRST TIME COMMENTER LOVE THE SHOW ;-) ... Seriously, I've been a subscriber of yours for a while, for numerous well-earned (by you) reasons. But I'm suggesting you re-do this (or at least edit) this particular video, because starting at 19:42, the entire concept of MVVM start to get muddy... AT 19:42 you start simply referring to the "withoutMVVM" class as your "View", but to anyone watching your video, the whole idea is they DON'T yet understand MVVM, so you're NOT helping them understand MVVM by referring to a class named "withoutMVVM" as the "View" :-| Suggestion: at 19:42 simply RENAME the "withoutMVVM" class as "CustomerView" , since at that point many/most viewers WILL get that this class now ONLY is responsible for the VIEW, so why NOT simply re-name it :-) ... RESULT: viewers will see the 3 classes you're trying so hard to explain: 1. CustomerView 2. CustomerViewModel and 3. CustomerModel :-) PLEASE don't take offense at this suggestion. YOU MUST CONTINUE POSTING, as you are among the BEST Subject Matter Experts I have ever bothered to watch on these often-butchered topics. Without YOUR posts, RU-vid is filled with RU-vid-savvy youngsters all "high on themselves", and using 3 stickynotes about a waiter in a restaurant to explain MVVM, and the world is lost. You are the ONLY one I've seen who explains the WHY and the LIMITATIONS of MVVM as a GUI-focused separation-of-responsibilities GUI architecture pattern. KEEP UP THE GREAT WORK !

nice video

I love love that

(25:50 lol) Great video! Finally understand MVVM.

3 laks students

25:56 Don’t be BOOL REDUNDANT!!! get { return obj.Married == “Married”; }

Is there any hindi developer anywhere who can teach good. Seems to me the answer is no. Your explanations are not good. Overly complex and not using good examples.

Well explained! Thank you so much!

hello! thanks for the tutorial!! I think some things have changed since, because whenever I wanted to set the IsMarried Property in the xaml,i got an error specifying that since the property (in the viewmodel) was readonly, i could not specify a value. So in this: the IsMarried="True" part was giving the error. I fixed it adding a setter to the IsMarried property in the viewmodel.

Very helpful, thanks.

Very good explanation and my concepts are very clear after watching your video. I tried to find your binding videos but not able to find. Can you please send me link of it?

MVVM (Model View View Model) is an GUI architecture pattern - MVVM is the evolution of the 3 layer architecture UI BL (Business Logic) DAL (Data Access Layer) - the 3 layer architecture violates SRP (Single Responsibility Principle) (because some layers are performing extra work which they are not supposed to do) - MVVM solves the "glue code" between UI and business logic layer (the "glue code" between business logic layer and data access layer is solved by repository pattern) - types of glue code: (the "owners" of this "glue code" is the UI code behind, which means some business logic codes are now part of the UI [typically at .xaml.cs file of our UI]) - binding/mapping code e.g.: txtCustomerName = customer.Name; - this code sends data from the ui to the business logic layer or probably takes the data from the business logic layer to the ui - transformation code e.g.: if (person.Gender == "M") { chkGender.IsChecked = true; } else { chkGender.IsChecked = false; } - data formats of the business logic layer and the ui can be different like the code above, the business logic layer's property (Gender) has values M for male and F for female, but when this data is displayed in the UI it is a checkbox (The UI doesn't understand "M" and "F" the UI only understands true or false) - When we use MVVM architecture, we divide the project into three layers: View View Model Model - in MVVM each layer handles its own responsibilities [VIEW] - the view will refer the viewmodel (by "adding a reference") - the view will invoke the viewmodel and the view model will invoke the model - all the calls FROM the view will come TO the viewmodel, and the viewmodel will send those calls(FROM the view) TO the model [VIEWMODEL] - the viewmodel will refer the model (by "adding a reference") - the viewmodel will be "using" the model - has the logic that binds the View and the Model - is a class library - the view model will invoke the model - whatever data you are exposing from a view model it should be of the least denominator type (do not try to use UI specific data type / UI technology specific data type) [MODEL] - the (most typically) real life object that you are trying to create - is responsible for exposing data in a way that is easily consumable by WPF Advantages of MVVM - Contain changes - when we make changes in one place, we don't have to change all across our project - Increased reusability