The driving force behind the MVC architecture is the controller. It returns the appropriate view and model for a request, but that is not the end of the story. In ASP.NET MVC, the controller is much more powerful. I will go deep into the infrastructure of the controller. You will discover that there is much more to this powerful framework than is shown in typical examples, and you will be able to use this knowledge for business scenarios that go beyond serving simple web pages.

1. MVC Controller Architecture Deep Dive

2. Holistic Look Where do controllers fit?

3. Simple Application A web site Abstraction costs higher than return Does not integrate with business processes Solo project

4. Simple Application Controller is the life of this app!

5. Simple Application Controller View Model

6. Layered Application More thought placed in design Integrates into larger infrastructures Abstraction necessary for reuse Team project

7. Layered Application Controller is the public interface

8. Layered Application Presentation Layer Crosscutting Concerns Controller View ViewModel Business Layer Model Workflow Component Data Access Layer DAL Component Gateway

9. Enterprise Application Complexity determined by business needs But strive for simplicity And reusability Will integrate into larger infrastructure

10. Enterprise Application Controller is still the public interface

11. Enterprise Application BUT

12. Enterprise Application It may be the life of an app if small…

13. Enterprise Application This is reduced… Web App Public Service Console App WPF App Workflow Service Business Service Data Service DB

14. Enterprise Application It probably looks like this...

15. The Controller Designing the perfect cog

16. Question Should I use repositories?

17. Should I Use Repositories? Yes

18. Should I Use Repositories? Only composition logic Encapsulate and abstract other logic

19. Considerations Flexibility Maintainability Related entities Are you using more than one repository per controller?

20. DEMO Encapsulation is simple

21. Question Do I need one repository per model?

22. One Repository Per Model? No

23. One Repository Per Model? Probably

24. Repository Style Coarse-Grained IEventRepository Fine-Grained IEventRepository IAttendeeRepository

25. Question How do I transition to n-tier?

26. Transition to n-tier? Easier

27. Transition to n-tier? If you followed my previous recommendations

28. Breaking It Up Presentation Layer Crosscutting Concerns Controller View ViewModel Business Layer Model Workflow Component Data Access Layer DAL Component Gateway

29. DEMO Moving to a tier Without affecting your Controller!!!

30. The Controller Routing Verbs Action Results Standard Controllers Custom Controllers

31. Routing HTTP Request web.config Global.asax Favor Resources

32. Routing Physical Controllers Logical Routes

33. DEMO Routing

34. Verbs HTTP Methods AcceptVerbs Attribute RESTful CRUD GET PUT POST DELETE

35. Verbs HEAD OPTIONS CONNECT TRACE Custom Verbs

36. DEMO Verbs

37. Action Results Controllers do something when called Standard action results ViewResult JsonResult ContentResult EmptyResult FileResult HttpUnauthorizedResult

38. Action Results More Standard actions JavaScriptResult RedirectResult RedirectToRouteResult Make your own!

39. DEMO Custom Action Results

40. Standard Controllers Great for standard web applications Convention-based Even non-standard controllers are convention based when used with views

41. Custom Controllers Can decorate the standard class Can inherit from ControllerBase Can implement IController Use for non-standard applications or for more control

42. DEMO Custom Controllers

43. Controller as a Service MVC apps are typically web sites They can also be web services Do you have a mixed site/service? It can also be a pure service without JSON

44. DEMO Controller as a Service

45. Resources Software Application Developers http://msdn.microsoft.com/ Infrastructure Professionals http://technet.microsoft.com/ technetindia msdnindia @technetindia @msdnindia

46. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.