lradunovic

separation of layers with Web Application. Again you can put everything in a code behind page, it comes down to individual programmer and his skills set to make true separation between data, business layer and presentation.

Code behind is not a good example of separation because your code is still very tightly coupled to your .aspx page. In most cases you have 1 code behind file per .aspx file, that's very tight coupling. With MVC you can literally use any view you want with a controller since the controller knows nothing about the view. For example I can reuse a controller across multiple views to support mobile vs web, or I can reuse controllers across multiple projects with similar views. You can't do that with webforms.

You also seem to be ignoring the testing aspect. Unit Testing is an extremely important task and helps mitigate many potential bugs (when done correctly). Testing ASP.NET MVC is orders of magnitude easier with asp.net mvc because you don't need a running web server.