ASP.NET Web API 2 Recipes 指南：配置、自定义、安全和测试

5星 · 超过95%的资源需积分: 10 63 浏览量更新于2024-07-23 3 收藏 3.73MB PDF 举报

ASP.NET Web API 2 Recipes ASP.NET Web API 2 Recipes是一本关于ASP.NET Web API 2的实践指南，旨在帮助开发者更好地理解和使用ASP.NET Web API 2框架。下面是对该书籍的知识点总结：关于作者和技术审阅者本书的作者是一名经验丰富的开发者和技术专家，对ASP.NET Web API 2框架有深入的了解和实践经验。技术审阅者也是一名有经验的开发者和技术专家，对本书的内容进行了严格的审核和修改。 ASP.NET Web API 2概述本书的第一个章节对ASP.NET Web API 2框架进行了概述，介绍了其核心概念、特点和应用场景。开发者可以通过本章节了解ASP.NET Web API 2的基本原理和设计理念。 ASP.NET Web API 2 Outside of IIS 第二章节讨论了ASP.NET Web API 2在IIS之外的应用场景，包括使用自承载、OWIN和 Katana框架等。开发者可以通过本章节了解如何在非IIS环境中使用ASP.NET Web API 2。路由第三章节详细介绍了ASP.NET Web API 2的路由机制，包括路由的配置、路由模板和路由约束等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的路由机制来实现灵活的路由控制。内容协商和媒体类型第四章节讨论了ASP.NET Web API 2的内容协商机制，包括媒体类型、内容协商算法和格式化数据等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的内容协商机制来实现灵活的数据格式化。配置和自定义第五章节介绍了ASP.NET Web API 2的配置和自定义机制，包括应用程序配置、服务配置和自定义组件等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的配置和自定义机制来实现灵活的应用程序配置。 HTTP和ASP.NET Web API 第六章节讨论了ASP.NET Web API 2对HTTP协议的支持，包括HTTP方法、状态码和头信息等。开发者可以通过本章节了解如何使用ASP.NET Web API 2来实现基于HTTP的Web服务。异常处理、故障诊断和文档第七章节介绍了ASP.NET Web API 2的异常处理机制，包括异常类型、错误处理和日志记录等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的异常处理机制来实现可靠的错误处理。跨域和推送通信第八章节讨论了ASP.NET Web API 2的跨域和推送通信机制，包括CORS、JSONP和Webhooks等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的跨域和推送通信机制来实现灵活的跨域通信。依赖注入第九章节介绍了ASP.NET Web API 2的依赖注入机制，包括服务容器、依赖注入模式和生命周期管理等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的依赖注入机制来实现灵活的组件管理。安全第十章节讨论了ASP.NET Web API 2的安全机制，包括身份验证、授权和加密等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的安全机制来实现可靠的安全保护。测试第十一章节介绍了ASP.NET Web API 2的测试机制，包括单元测试、集成测试和功能测试等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的测试机制来实现可靠的测试。 OData 第十二章节讨论了ASP.NET Web API 2对OData协议的支持，包括OData模型、OData查询和OData数据类型等。开发者可以通过本章节了解如何使用ASP.NET Web API 2的OData机制来实现灵活的数据交换。

CHAPTER 1 ■ WEB API IN ASP.NET

Name = form["Name"],

Gender = form["Gender"]

};

//process user...

//rest omitted for brevity

}

public class UserController : ApiController

{

public HttpResponseMessage Post(UserModel user)

{

//process user...

//rest omitted for brevity

}

1-4. Link from MVC Controller to API Controller and Vice Versa

Problem

You would like to create direct links from ASP.NET MVC controllers to ASP.NET Web API controllers and the other

way round.

Solution

You can create links to controllers using an instance of System.Web.Http.Routing.UrlHelper, exposed on the

base ApiController (as the Url property), as well as on the RequestContext, which is attached to an instance of

HttpRequestMessage. To achieve this, you need to call the Link or Route method and pass in the name of the MVC

route and the route defaults (controller name, action name, and relevant action parameters).

On the MVC controller side, System.Web.Mvc.UrlHelper, hanging off the base MVC base Controller class, is

able to generate Web API links via the HttpRouteUrl method.

How It Works

It is a common requirement, when using ASP.NET Web API as part of an existing MVC application, to be able to cross

link between the two types of controllers. When creating links to MVC controllers from Web API, you actually use the

exact same methods as when creating links between Web API controllers: Link or Route on the UrlHelper. The reason

why this is possible is that ASP.NET Web API will find the route by name, and then call the GetVirtualPath on that

route to resolve a link to it. If the route happens to be registered as an MVC route, it will be of type System.Web.Route

and its particular implementation of GetVirtualPath will be used. It’s important to remember that the Link method

will generate an absolute link, while the Route method will generate a relative one.

In the opposite direction, when linking from MVC to Web API, the HttpRouteUrl method is not an extension method

introduced by the ASP.NET Web API assemblies, but rather a class member of UrlHelper, inside the System.Web.Mvc

DLL. This helper uses a private constant called httproute, which is added to the RouteValueDictionary every time

you use HttpRouteUrl. This way, a route can be identified as pointing to ASP.NET Web API.

Note ■ Recipe 3-12 is dedicated to further exploring and understanding the engine behind generating links to routes.

www.it-ebooks.info

CHAPTER 1 ■ WEB API IN ASP.NET

1-5. Use Scaffolding with ASP.NET Web API

Problem

You’d like to rapidly bootstrap an ASP.NET Web API solution.

Solution

ASP.NET Scaffolding has supported ASP.NET Web API from the very beginning. To use scaffolding to add Web API

controllers to your project, right-click the Controllers folder in your solution, and choose Add ➤ New Scaffold Item.

From there, out of the box, you can select one of the following:

Web API 2 Controller•

Web API 2 Controller with actions, using Entity Framework•

Web API 2 Controller with read/write actions•

Web API 2 OData Controller with actions, using Entity Framework•

Additionally, scaffolding templates with attribute routing can be downloaded from NuGet:

Install-Package Microsoft.AspNet.WebApi.ScaffolderTemplates.AttributeRouting.CSharp

How It Works

The proper, full name for the scaffolding functionality is ASP.NET Scaffolding, and it is a T4-based code generation

framework for ASP.NET. T4, a Text Template Transformation Toolkit, is a template-based code generator that has been

part of Visual Studio since version 2005.

Visual Studio 2013 introduced support for the excellent Scaffolded Items feature, allowing you to quickly generate

bootstrapping code for your ASP.NET applications. With Visual Studio 2013 Update 2, some terrific extensibility points

have been added, introducing the possibility for template customizations, giving you the ultimate flexibility when it

comes to code generation.

The built-in scaffolding templates are installed in your Visual Studio installation folder, and can be customized

from there. For example, if you use the standard Program Files folder, that would be C:\Program Files (x86)\

Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web\Mvc\Scaffolding\Templates. If you

modified any of the templates there, the changes will obviously have a global effect. If you would like to customize the

templates on a per project basis, there are two ways to do so:

Install SideWaffle (• sidewaffle.com), a Visual Studio extension dedicated to template

management. Then use the regular “add” dialog, and choose Web ➤ SideWaffle ➤ ASP.NET

Scaffolding T4. This will create a new CodeTemplates folder in your solution, containing the copies

of all of the global scaffolding templates, which you can edit there to suit your solution’s needs.

Copy all of the files from the global scaffolding templates folder to your ASP.NET project •

manually, into a top-level folder named CodeTemplates (name is important). This copies both

C# and VB.NET templates, but you can get rid of the ones you don’t need by hand. Make sure

to include the files into your project.

The Code

Let’s walk through a basic scaffolding process for a Web API controller with Entity Framework Code First model.

The model is shown in Listing 1-13.

www.it-ebooks.info

剩余394页未读，继续阅读

yuvillagearcher

粉丝: 5
资源: 17

ASP.NET Web API 2 Recipes 指南：配置、自定义、安全和测试

ASP.NET Web API 2实战指南：问题解决与深度解析

ASP.NET MVC 4 Recipes 入门指南

ASP.NET与jQuery实践指南

ASP.NET Web API 2 Recipes（英文pdf）

ASP.NET Web API 2 Recipes

Apress.ASP.NET.MVC.4.Recipes.Feb.2013

Apress.dot.NET.Test.Automation.Recipes.A.Problem.Solution.Approach.May.2006.pdf

apress.dot.net.test.automation.recipes.a.problem.solution.approach.may.2006

ASP.NET.MVC.4.Recipes

Apress.ASP.NET.MVC.4.Recipes

最新资源