MVP-VM (Model View Presenter-View Model)

Question

2.00/5 (2 votes)

See more:

I'm working a C# winForm project and I'm applying MVP-VM...I'm not understanding the benefit(s) of binding my UI widgets to my "ViewModel" which is actually just a reflection of my Model. Seems to me like I'm just adding another layer of abstraction unnecessarily. Why not just pass my Model(businessObj) to my View(Form) and bind it to the appropriate UI widget(s) instead of binding the ViewModel?

Posted 23-Jul-12 11:06am

d.allen101

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Christian Graus · Answer 1 · 2012-07-23T12:03:00

Solution 1

Often your view model will contain all the data pertaining to a specific task, which will cross boundaries of different Model objects. I find that with MVC all the time, I have my model class, plus a few bits of info I need in just this one page to know how I am dealing with that data.

Posted 23-Jul-12 12:03pm

Christian Graus

Comments

d.allen101 23-Jul-12 19:31pm

not sure I understand what you are saying. let's say I have two different models: 1)Customer 2)Product. are you saying that my viewModel would contain the attributes of both of these models?

Christian Graus 23-Jul-12 19:32pm

A viewmodel for a page that shows a list of products that have been ordered by a customer would probably have elements of both, yes. My models in MVC all come from our Entity Framework classes for the DB, so whenever data I need crosses two tables, my viewmodel will contain data from more than one model.