ASP.NET MVC Solution Best Practices
- Day 1
- Speakers: Steve Smith
- 17,870 Views
- 3 Comments
Developers choose ASP.NET MVC because it provides for more control over the resulting HTML, better separation of concerns, and better testability. But these benefits are only fully realized if the project and solution is set up properly. Otherwise, it's very possible to create a tightly coupled Big Ball of Mud solution that's difficult to test and change. In this session, we'll create a 'Walking Skeleton' solution of a simple web application using ASP.NET MVC 4 that shows off certain best practices of creating maintainable, loosely coupled solutions.
Comment on this Session
Already have a Channel 9 account? Please sign in
Follow the Discussion
Great no-nonsense presentation on organizing an ASP.NET MVC solution into "Core" (Interfaces, Models, and Services), "Infrastructure" (Repositories, Data Access context/helpers, 3rd-Party Service Implementations like Email, Payment, etc), Web (Controllers, Views, ViewModels, and HTML/CSS/JSS) and "Tests" projects. The speaker takes you from the starting point of a default ASP.NET MVC 4 project ( examples apply to any version of ASP.NET MVC) and refactors the code into multiple projects using what he calls the "Onion Architecture". Before viewing, I'd recommend that you should have some experience with creating ASP.NET MVC sites and a familiarity with writing Unit Tests. The full source code for the sample "Guestbook Application" is available on the presenter's blog: http://ardalis.com/aspconf-2012-sessions
Thanks
Very Useful Session and Solves the problem of "separation of Concern".
Great presentation. Learned a lot. Can't get to the sourcecode though, site seems to be down..
Remove this comment
Remove this thread
close