MVC is part of the asp.net framework. It is a programming model which helps you create an asp.net web application, but MVC is much slicker and cleaner then asp.net Webforms environment.

This short video discusses the benefits and drawbacks of using the MVC Model-View-Controller approach versus the web forms. Model–view–controller (MVC) is an architectural pattern used in software development. The pattern isolates “domain logic” (the application logic for the user) from the user interface (input and presentation), permitting independent development, testing and maintenance of each (separation of concerns).

The last major piece of the ASP.NET MVC Framework is the View engine. This video explores the default View Engine in MVC2, the WebForms View Engine, and shows how you can use views to display information to the user.

Video Source: http://net.tutsplus.com/tutorials/asp-net/asp-net-from-scratch-views/

ASP.NET MVC is great for building one off applications to solve specific problems, but not much time is given to how we can use the extensibility model built into the framework to allow our own plug-ins to add/modify functionality or create theming systems for multiple customers.
Watch this video on oredev.org

This video explores into URL routing in the MVC framework and examine how a request can be routed to a controller and action method. You’ll learn how to use constraints to gain better control over your routers, and also discuss best practices in adding routes to the route table.