Professional Model View Controller (MVC) Interview Preparation Guide

Download PDF

Layout pages, can define sections, which can then be overriden by specific views making use of the layout. Defining and overriding sections is optional.

1. .cshtml - If the programming lanugaue is C#
2. .vbhtml - If the programming lanugaue is VB

Razor syntax makes use of @* to indicate the begining of a comment and *@ to indicate the end. An example is shown below.
@* This is a Comment *@

To have a consistent look and feel when using razor views, we can make use of layout pages. Layout pages, reside in the shared folder, and are named as _Layout.cshtml

No, by default content emitted using a @ block is automatically HTML encoded to protect from cross site scripting (XSS) attacks.

The escape sequence character for @ symbol, is another @ symbol

<%= %>

@ symbol

1. Razor
2. .aspx

Result Filter

Yes

Exception Filters

Yes

1. Action Method
2. Controller
3. Application

Authorization filter

1. RequireHttpsAttribute
2. AuthorizeAttribute

1. Authorization filters
2. Action filters
3. Result filters
4. Exception filters

1. Authorization filters
2. Action filters
3. Response filters
4. Exception filters

Action Filters allow us to add pre-action and post-action behavior to controller action methods.

1. A Physical File is Found that Matches the URL Pattern - This default behaviour can be overriden by setting the RouteExistingFiles property of the RouteCollection object to true.
2. Routing Is Explicitly Disabled for a URL Pattern - Use the RouteCollection.Ignore() method to prevent routing from handling certain requests.

1. Use regular expressions
2. Use an object that implements IRouteConstraint interface

Use a route with a catch-all parameter. An example is shown below. * is referred to as catch-all parameter.
controller/{action}/{*parametervalues}

To add routes to a webforms application, we use MapPageRoute() method of the RouteCollection class, where as to add routes to an MVC application we use MapRoute() method.

{resource}.axd/{*pathInfo}
This route definition, prevent requests for the Web resource files such as WebResource.axd or ScriptResource.axd from being passed to a controller.

{controller}{action}/{id}
No, the above definition is not a valid route definition, because there is no literal value or delimiter between the placeholders. Therefore, routing cannot determine where to separate the value for the controller placeholder from the value for the action placeholder.