How should I approach on applying WPF MVVM to a large scale application

Question

0.00/5 (No votes)

See more:

Hi,
We have a large scale winform application with more than 100 clients. Now we have decided to move forward & redesign the app with WPF. I have looked at some examples on MVVM Pattern & thought of below structure:

Server Side: Database -> WCF Service
Client Side: DataSource dll (plain data classes)
DataAccess dll (will refer to data source dll & perform database related operations)
BusinessLogic dll(will refer to DataSource & DataAccess dll)
UI_Model dll (will refer to DataSource dll & BusinessLogic dll)
UI (will refer to UI_Model dll)

Please note I have separated view(UI) from viewmoded (UI_Model) by creating a separate dll for viewModel, is it a correct approach? Or my view & viewModel should both remain in one project? I would appreciate if anyone can suggest me whether I am on a right track or required to change the structure.

Thanks

Posted 7-Oct-12 23:44pm

divyang_dv

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)

_Maxxx_ · Answer 1 · 2013-10-29T18:07:00

I'm not sure why you are using a UI_Model here? What would be there?

I normally consume POCO data classes in my view model - and either wrap them or otherwise present the information to the Views

I also separate my View and ViewModel into different projects in the solution, with the View project having a reference to the ViewModel project - that way I avoid accidentally referring to some View information from my ViewModel.

So I normally end up with:

VIEW binds to VIEWMODEL which uses DATAOBJECTS provided by BUSINESSLOGIC via DATASERVICES from SOMEDATASOURCES