Following the order of your questions:
1 // None. Web forms are based on the Smart Interface template, i.e. You control the application by recording event handlers. Smart UI has its own problems, but when it is completely based on the desktop, it works fine, in the sense that no significant “fiction” is included in the framework for its work. However, on the Internet, which works on HTTP without obsolescence, the main fantasy is introduced, essentially in the form of a ViewState, which contains the state of all controls when the page has been sent to the client browser. As a result, web forms introduce a complex level of complexity into your applications that exist only to support this ficiton. MVC eliminates this fiction.
: " , HTTP .
2//MVC HTTP. Front Controller, Page Controller, Page Controller Http, MVC HTTP-. , MVC , .
MVC , Webforms/Smart UI .
, , ASP.NET MVC ASP.NET HTTP " ", , , . , , , .
3//, , ! , - ui, MVC . , MVC ish (a la Dino Esposito), - ficiton. , ASP.NET MVC?
. , webforms mvc, - . " " - , , ( , ... Yuck!).
10 WizardController, - , . 3 webforms, -. .