ASP.NET MVC Fundamentals

MVC (Model-View-Controller) is a design pattern separating application logic into three interconnected components. Model handles data and business logic. View handles display and user interface. Controller handles user input and updates Model/View. 'Viewer' and 'Control' are not the standard terminology.

ASP.NET MVC 2.0 introduced multiple significant features including asynchronous controllers for better scalability, enhanced model validation support, and Html.RenderAction for progressive rendering/partial views. All three listed features were indeed new in MVC 2.0, making 'All of the above' the correct choice.

MVC Framework explicitly does NOT use view state (that's a Web Forms feature), which is one of its advantages for cleaner markup and better performance. MVC does support TDD, provides separation of concerns, and supports RESTful URLs - these are all benefits/usages, not things it doesn't do.

ASP.NET MVC 2.0 provides greater control over application behavior through improved separation of concerns, enhanced routing, and better abstraction over WebForms. While it gives some control over client IDs and reduces view state issues, its primary benefit is behavioral control.

ASP.NET MVC 2.0 runs on top of the ASP.NET runtime, meaning it fully supports existing ASP.NET features like Master Pages, User Controls, Caching, and built-in Authentication/Authorization mechanisms.

RouteTable is defined in Global.asax during Application_Start. This is the standard location where routes are registered in the MVC application startup lifecycle. Web.config and App.config are for configuration settings, not route definitions.

Strongly-typed view scaffolding in MVC includes multiple content template options: Create, Edit, Delete, Details, and List. All of these are standard scaffold templates available when generating strongly-typed views.

In ASP.NET MVC 2.0, Html Helper methods are the primary mechanism for rendering views. These helper methods generate HTML markup programmatically and are the standard way views are rendered. Page Events are a WebForms concept, not MVC.

MVC 2.0 includes 10 standard Html Helper methods including ActionLink, BeginForm, TextBox, DropDownList, CheckBox, RadioButton, ListBox, Password, Hidden, and TextArea. This is a specific factual question about the MVC 2.0 framework.

Unit testing in MVC allows testing all aspects of controller actions: the returned view, the ViewData dictionary, and the ActionResult type itself. This comprehensive testability is a key advantage of the MVC architecture.

ASP.NET MVC 2.0 includes several built-in action filters: OutputCache for caching, HandleError for error management, and Authorize for authentication/authorization. These are core filters provided by the framework.

By default, the controller treats all public methods as potential action methods. Non-public methods (private, protected) are not considered actions. Special attributes like [NonAction] can also exclude public methods from being actions.

ViewData is a specific dictionary object used to pass data from Controller to View in MVC. While Session can also pass data, ViewData is the designated mechanism for this controller-to-view communication pattern. ViewState is a WebForms feature.