Session
ASP.NET MVC Solution Best Practices
with Steve Smith
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.
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.
Have feedback? Submit an issue here.