Is that a best practice to keep business logic in Models in MVVM?

Question

0.00/5 (No votes)

See more:

Say I have a student class, in my observation creating and populating the test scores of a student (from a DB/Service) should be handled in a different class (possibly a factory pattern) is that a best practice? or should I populate the data from the student class?

Please advice!

-Vallarasu S.

Posted 19-Nov-11 6:07am

VallarasuS

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)

Vijay Bth · Answer 1 · 2011-12-07T03:16:00

MVVM if best practice for WPF prospect. By using this u can manage u application more efficiently. Because it separate ur UI with ur code files. So multiple user can work on same module. If u have change in ur UI the it will not much bother ur code. Coupling between module is very loose so every thing is very much independent.