How to communicate between the viewmodel and the model if the model is in a separate project?

Question

0.00/5 (No votes)

See more:

Hi all,

I am new to WPF and Entity Framework. I am planning to use MVVM pattern in a WPF client application and Entity Framework for model. For security reasons, I am keeping the model(Entity Framework) in a separate project i.e my client application will have only view and viewmodel. In this case which is the best way to communicate between model and viewmodel?

Thanks in advance...

Posted 19-Mar-13 0:15am

vinodkalanji

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-03-19T04:55:00

A separate project simply makes a separate assembly which should be referenced by other assemblies. It makes almost no differences compared to the monolithic solution. You only need to take into account access modifiers: if some type and it's member are to be accessed by a different assemblies, it should have public access modifier, or protected, for members of some base classes. Types and members to be accessed inside assembly only should be internal.

I hope you know how to reference assemblies. I would highly recommend to keep all referenced assemblies in one solution and use referencing by projects, using the "Project" tab in the "Add Reference" window (not "Browse" tab).

I all other respects, you use the declarations of another assembly in exact same way as in a monolithic solution,

—SA