<Disclaimer>This is personal notes of what I retained during the session. This can be incomplete, partially right or wrong. It is just  part of the notes I took and what retained my attention. Nothing prevents the user to get more information on their favorite web site.</Disclaimer>

The MVC pattern development for ASP.NET comes from the observation of several problems. First, the viewstate problem that drastically increase the payload of a page, and the difficulty to test a user interface due to the fact that the business logic is tightly coupled with the user interface.
That is why, among other drivers, the MVC pattern has been developed on top of the existing ASP.NET framework.
Basically, three roles are taking place in the pattern : the controller which is only responsible of collectng the user inputs, the model that is responsible to represent the underlying data and implements the business logic, and the view which has the only responsability of rendering the user interface.
This means that we are moving from a statefull web, using the webforms, towards a stateless model.
The MVC pattern has the advantage of being an alternative to the webforms, being testable and also extensible. Its components can also be replaced by your custom ones.
In Visual Studio, when a MVC Web application is created, it automatically asks if a unit testing project should be created. It is also possible to select the testing framework. On the project folder structure, folders are automatically created to store the views, the models and the controllers separately.