Downloaded 49 times
Uploaded byChris Eargle
Deep Dive: MVC Controller Architecture
The document provides an in-depth overview of the MVC controller architecture, emphasizing its roles in simple and enterprise applications and the importance of design for integration and reuse. Key considerations include the use of repositories, transitioning to n-tier architecture, and understanding routing and action results. It highlights the controller's function as the public interface in various applications, advocating for simplicity while managing complexity.
More Related Content
Similar to Deep Dive: MVC Controller Architecture
Deep Dive: MVC Controller Architecture
- 1.
- 2. Holistic LookWhere docontrollers fit?
- 3. Simple ApplicationA websiteAbstraction costs higher than returnDoes not integrate with business processesSolo project
- 4. Simple ApplicationController isthe life of this app!
- 5.
- 6. Layered ApplicationMore thoughtplaced in designIntegrates into larger infrastructuresAbstraction necessary for reuseTeam project
- 7. Layered ApplicationController isthe public interface
- 8. Layered ApplicationPresentation LayerCrosscuttingConcernsControllerViewViewModelBusiness LayerModelWorkflowComponentData Access LayerDAL ComponentGateway
- 9. Enterprise ApplicationComplexity determinedby business needsBut strive for simplicityAnd reusabilityWill integrate into larger infrastructure
- 10. Enterprise ApplicationController isstill the public interface
- 11.
- 12. Enterprise ApplicationIt maybe the life of an app if small…
- 13. Enterprise ApplicationThis isreduced…Web AppPublic ServiceConsole AppWPF AppWorkflow ServiceBusiness ServiceData ServiceDB
- 14. Enterprise ApplicationIt probablylooks like this...
- 15. The ControllerDesigning theperfect cog
- 16. QuestionShould I userepositories?
- 17. Should I UseRepositories?Yes
- 18. Should I UseRepositories?Only composition logicEncapsulate and abstract other logic
- 19. ConsiderationsFlexibilityMaintainabilityRelated entitiesAre youusing more than one repository per controller?
- 20.
- 21. QuestionDo I needone repository per model?
- 22. One Repository PerModel?No
- 23. One Repository PerModel?Probably
- 24.
- 25. QuestionHow do Itransition to n-tier?
- 26.
- 27. Transition to n-tier?Ifyou followed my previous recommendations
- 28. Breaking It UpPresentationLayerCrosscutting ConcernsControllerViewViewModelBusiness LayerModelWorkflowComponentData Access LayerDAL ComponentGateway
- 29. DEMOMoving to atierWithout affecting your Controller!!!
- 30. The ControllerRoutingVerbsAction ResultsStandardControllersCustom Controllers
- 31.
- 32.
- 33.
- 34. VerbsHTTP MethodsAcceptVerbs AttributeRESTfulCRUDGETPUTPOSTDELETE
- 35.
- 36.
- 37. Action ResultsControllers dosomething when calledStandard action resultsViewResultJsonResultContentResultEmptyResultFileResultHttpUnauthorizedResult
- 38. Action ResultsMore StandardactionsJavaScriptResultRedirectResultRedirectToRouteResultMake your own!
- 39.
- 40. Standard ControllersGreat forstandard web applicationsConvention-basedEven non-standard controllers are convention based when used with views
- 41. Custom ControllersCan decoratethe standard classCan inherit from ControllerBaseCan implement IControllerUse for non-standard applicationsor for more control
- 42.
- 43. Controller as aServiceMVC apps are typically web sitesThey can also be web servicesDo you have a mixed site/service?It can also be a pure service without JSON
- 44. DEMOController as aService
- 45. ResourcesSoftware Application Developershttp://msdn.microsoft.com/InfrastructureProfessionalshttp://technet.microsoft.com/technetindia msdnindia@technetindia@msdnindia
- 46. © 2011 MicrosoftCorporation. 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.
Editor's Notes
- #45 The title of this demo is actually funny to me. Controllers are already services. A request comes in, it is routed to the appropriate action on a controller, and a response is sent back out. Controllers are services that typically respond with information to be rendered in a browser.