GUI and Web Frameworks

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.

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.

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.

In ASP.NET MVC, views use the .aspx extension for standard views and .ascx extension for partial views or user controls. The .html extension is not a standard ASP.NET MVC view extension - HTML would be the output format, not the file extension.

ASP.NET MVC 2.0 provides four main action filter interfaces: IAuthorizationFilter (for authorization), IActionFilter (for pre/post action execution), IResultFilter (for pre/post result execution), and IExceptionFilter (for exception handling). All of these interfaces are part of the action filtering framework.

ASP.NET MVC 2.0 works with Visual Studio 2008 SP1 (Service Pack 1 is required for MVC support) and Visual Studio 2010 (which includes MVC 2 out of the box). Standard Visual Studio 2008 without SP1 does not support ASP.NET MVC 2.0.

ASP.NET MVC uses clean URLs without file extensions. Option A shows the standard controller/action pattern. Option C shows the pattern with an input parameter as part of the URL path. Options B and D incorrectly add .aspx extension or use querystring syntax for parameters, which are not standard MVC routing patterns.

Controller action methods must be public (to be accessible via HTTP), should not be static (instance methods are required for context and dependency injection), and can have ref and out parameters. They cannot use generic type parameters directly as part of the method signature in the action invocation context.

The Model Browser is the Visual Studio tool window integrated with the ADO.NET Entity Data Model Designer. It provides a hierarchical view of the entity types, associations, and properties defined in the .edmx file. The Model Browser allows developers to navigate and inspect the conceptual model structure, while the Model Designer surface provides the visual layout.

In the WF4.0 designer, OutArguments are typically accessed by assigning them to variables. The designer binds these arguments to variables that can then be used elsewhere in the workflow. This is the standard pattern for extracting output from activities and workflows. InArguments are for input, not output access.

The ResumeBookmark method requires two parameters: the bookmark name and the value to pass to the resumption point. WorkflowApplication (not WorkflowInvoker) is the correct host type for operations involving bookmarks. The method signature is ResumeBookmark(bookmarkName, value), where value can be null if no data needs passing.