Design pattern for Controller in ASP.NET MVC3

Question

0.00/5 (No votes)

See more:

I have WCF Services exposed by dynamics CRM 2011, and a ASP.NET MVC3 portal to consume these services.

I have to make call to WCF services from controller and I don't want to make call to WCF services directly from controller. I can think of following patterns

•Service Facade

•DI and IoC at controller level

What is the best practice in terms of patterns for this scenario.

Thanks

Posted 19-Oct-11 20:27pm

VishalHealthcare

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)

Berman Felix · Answer 1 · 2011-11-22T23:39:00

Hi! In general, accessing web (or WCF) services should be encapsulated by the Model part of the MVC pattern. Since ASP.NET MVC does not prescribe rules of how your model classes should be organized, you have to make those decisions by yourself. Make your model classes expose interface(s) that will be consumed by MVC controllers. Those interfaces can be the contracts of CRM services themselves, or something different, depending on your situation -- they will be the Service Facade that you mentioned. Use IoC/DI to let MVC controllers obtain object instances for the interfaces. And (just to make sure): AsyncController should be used in this scenario. That's it. Please feel free to follow up with any additional questions.