ASP MVC's is a breath of fresh air after ASP.NET's general awfulness.

In a nutshell, it's getting rid of ASP.NET's illusion of a stateful webForm, and returning to how the web works: views created in HTML to render models (domain or view) while leaving the handling of the request to controllers -- rather than routing them back to the control to process as an event handler.

Things that an ASP.NET developer need to get used to are that routing in ASP.NET was per file, but MVC programs work rather differently: URLs are mapped to Action Methods (ie public methods that return ActionResults) of Controllers that subclass Controller [: ControllerBase : IController]  derived classes.

Note that exposing all public methods of a class can be a bit frightening to an ASP.NET developer -- but need not be. First of all, we are talking about the public methods of Controllers: classes specifically geared to handling requests, and secondly, one can 'opt out' with NoActionAttribute.

Another thing that asp.net developers have to get used to are conventions. MVC is a conventions based framework, where things are named a certain way to fit well-known patterns. This actually is good: it makes for less wiring (more can be done by the framework auto-magically) and therefore saves you time.