a quick overview of MVC

1. What is ASP.NET MVC?
A better way to build the web.

2. MVC Pattern

3. ASP.NET MVC Goals
• Leverage ASP.NET core features
• Loose coupling and extensibility
• Testability
• Tight control over markup
• Separation of concerns
• Convention over configuration
• Better team development
• Strong community of web developers

4. How it works.

5. How it works.

6. How it works.

7. How it works.

8. How it works.

9. Life of a Http Request

10. How MVC is typically built.
Models
- contains the bulk of your application logic. (ie. db
access, security, aggregations, etc )
- possibly your Entity Framework model, Linq2SQL, a
repository, or a service layer.

11. How MVC is typically built.
Views
- contains html, styling and JavaScript for the
application layout and pages.
- may also contain Ajax calls that getpost data for
Async features.
- Other client-side frameworks could be used here, like
jQuery, BackBone.js, Knockout.js

12. How MVC is typically built.
Controllers
- this is the application’s entry point, which handles
the http requests (Actions) and any required
parameters.
- for best practices, “Actions” in a controller should be
as minimal as possible.

13. Why it’s better.
• Open source: http://aspnetwebstack.codeplex.com/
• NuGet.org (9000+ nuget packages)
• Embraces html5 & javascript
• Active community (stackoverflow, github)
• Learned from other successes (Rails, Zend)