Errata

Code listing 1-5 on page 23 refers to using the HttpService class (no namespace listed), but a search of classes in the .NET framework does not return this class. Traditionally using Web API you would choose to use the System.Net.Http.HttpClient class.

If also tried importing the Nuget package for Web Api (currently v 2.1) and it doesn't include an HttpService class.

If HttpService needs to be pulled in a special fashion it should be documented in the chapter.

Answer B "Create an HttpService and connect using Get(URL)" is not a valid answer to question #2.

The ASMX will return a SOAP response - and the HttpService example on page 23 clearly refers to this approach as "Using the HttpService class to get output from a ***REST URL***"

The traditional way to consume an ASMX web service is by creating a proxy class. Refer to page 22 "Consuming a web service in ASP.NET MVC 4 in Visual Studio is as simple as using the Add
a Service Reference command."

Thanks.

None of the choices is correct.
"MapRequestHandler" is raised after the appropriate HttpHandler is selected to respond to the request. So we cannot redirect the request to a different handler; than is in the routing table, in that event.

The right answer is to handle the "PostResolveRequestCache" event "ASP.NET Routing"

ASP.NET routing is a request-dispatching mechanism that lets us associate a certain URL with a handler that can process requests made to that URL. This association is done by registering the "routes" that define which handler to invoke for a particular URL path. When a request is made to a Web server ASP.NET routing looks up the requested URL path in the list of registered routes. If the route is found, the corresponding handler for that route is invoked to process that request.

ASP.NET routing is implemented as a managed-code module that plugs into the IIS request-processing pipeline at the Resolve Cache stage (PostResolveRequestCache event) and at the Map Handler stage (PostMapRequestHandler event). ASP.NET routing is configured to run for all requests made to the Web application.

During the PostResolveRequestCache event, the module looks through a routing table (a collection of route objects) for a route that matches the requested URL path. If a match is found, the module obtains a reference to the handler that corresponds to that route and saves the reference as part of the current HTTP context. A handler can be any .NET Framework object that implements the System.Web.IHttpHandler interface. If no route is found, the module does not do anything, and the URL falls through and is processed normally (typically by matching it to a file on disk).

During the PostMapRequestHandler event, the module checks if the HTTP context contains any information about a handler. If it does, ASP.NET routing uses the information to set the Handler property of the current HTTP context. This ensures that during the Execute Handler stage, IIS will execute the handler that was selected by the routing module. If that information is not set, then the module does not do anything and the URL falls through to let IIS make a handler selection.

The book states:

A base template inherits the System.Web.Mvc.ViewMasterPage namespace, regardless of view engine, as shown by the main tag in _Layout.cshtml:

<%@ Master Language="C#" Inherits="System.Web.Mvc.ViewMasterPage" %>

However _Layout.cshtml does not have a tag like this - look at the following page (Listing 2-1 on 87) for a sample _Layout.cshtml - without this tag. I believe this is from a Site.Master file.

Reg. JsonRequestBehavior.AllowGet enum:

It's NOT for "which ensures that if the user accepts the returned value, the validation will not run again"
By default, the ASP.NET MVC framework does not allow us to respond to an HTTP GET request with a JSON payload. If we need to send JSON in response to a GET, we will need to explicitly allow the behavior by using JsonRequestBehavior.AllowGet as the second parameter to the JSON method. However, there is a chance a malicious user can gain access to the JSON payload through a process known as JSON Hijacking. So we usually do not return sensitive information using JSON in a GET request (not applicable with this example).

That snippet is required for all automatic client validations of model-based data annotations; not only for remote validation.
Please, mention that in the preceding paragraph. That snippet should be shared between the two sections "Views" and "Using Remote Validation".