ASP.NET Web API 入门与进阶教程

需积分: 10 139 浏览量更新于2024-07-22 收藏 1.79MB PDF 举报

"ASP.NET Web API Succinctly 是一本由Emanuele Del Bono编写的PDF电子书，专门针对ASP.NET Web API进行全面介绍和入门进阶的教程。此书由Syncfusion Inc.出版，并提供免费下载，但仅限于个人或教育用途，禁止任何形式的再分发。在www.syncfusion.com完成注册后，读者可以免费获取这本书。书中明确指出，作者和版权所有者不对任何信息提供保修，也不承担由此产生的任何索赔、损害或其他责任。如果接受这些条款，使用本书即视为同意这些条件。Syncfusion、Succinctly、Delivering Innovation with Ease、Essential和.NET Essentials是Syncfusion Inc.的注册商标。" ASP.NET Web API是Microsoft开发的一个用于构建RESTful服务的框架，它允许开发者使用.NET Framework创建HTTP服务，这些服务可以被各种不同的客户端访问，包括浏览器和移动设备。Web API的核心是基于HTTP协议，这使得它非常适合构建面向Internet的应用程序。在本书中，作者Emanuele Del Bono将带领读者深入理解ASP.NET Web API的关键概念和技术。他会从基础开始，介绍如何设置一个新的Web API项目，包括配置路由和控制器。Web API的控制器是处理HTTP请求的主要组件，它们类似于MVC（模型-视图-控制器）架构中的控制器，但专注于处理HTTP操作，如GET、POST、PUT和DELETE。接下来，书中可能会涵盖如何创建模型类，这些类定义了服务公开的数据结构。数据绑定和验证是Web API中的重要部分，允许模型数据与HTTP请求之间进行自动转换和验证。 Emanuele Del Bono还会讲解如何实现过滤器，这些是可重用的代码片段，可以应用于整个API或特定的控制器动作，用于执行如身份验证、授权或日志记录等任务。此外，错误处理和异常处理也是Web API开发中不可忽视的部分，本书会指导读者如何优雅地处理和返回错误信息。对于更高级的主题，如单元测试、集成测试以及如何部署和发布Web API服务，作者也会有所涉及。此外，可能还会讨论与其他技术（如OData用于数据查询，Swagger用于API文档，或者OAuth 2.0用于身份验证和授权）的集成。最后，书中可能会探讨一些最佳实践和设计模式，帮助开发者构建可扩展、可维护且高效的Web API服务。通过学习这本书，读者不仅可以掌握ASP.NET Web API的基本用法，还能了解到如何构建健壮的、符合REST原则的服务，从而提升其在Web开发领域的专业技能。

POST

When POST is used to create a resource, the resource data is sent to

the server as part of the request’s body. The server responds with a

status 201 CREATED if everything goes well. When a new resource is

created, it’s a best practice to use the Location header in the

response to specify the URI of the newly created resource. This

adheres to the HATEOAS principle.

PUT

PUT is used to modify the resource. The URI specifies the resource

that we want to modify and the body contains the new resource

values. The response HTTP status code should be 200 OK or 204

No content if the response doesn’t contain the modified resource. It

is not necessary to return the URI of the resource itself in the

Location header because the client already knows it. PUT has to be

idempotent, which means that the result of a successful request is

independent of the number of times it is executed. It has to be

possible to place two equal calls to the server, and the server should

not return errors; the second call simply redoes the update even if it

does not change the resource.

DELETE

DELETE is used to delete the resource. The result could be a 200 OK or 204 NO CONTENT if the

response does not contain a body. It could be 404 Not Found if the URI is not correct and the

resource cannot be found.

Summary

This is just a short introduction to REST, just what we need to correctly use the ASP.NET Web

API. REST is a vast topic and entire books have been written about it. We just examined some

principles and how the HTTP verbs are used to work with resources.

HATEOAS

(Hypermedia as the

Engine of Application

State)

In a REST application, the

client needs to know as little

information as possible to

use the application. Ideally,

the only thing the client

needs to know is the URI of

the entry point. All other

URIs should be provided by

the server using location

headers or other

mechanisms (rel links, for

example) to inform the client

where the other resources

are. This way the client and

the server are not tied and

the server could change the

location of the resource

without breaking the client.

This is at the base of the

well-designed REST API.

Inside this class we find all the default verbs to manipulate the Value resource: GET, POST, PUT,

and DELETE. The name of the methods here matters, since the ASP.NET Web API runtime uses

conventions to find the action to call against an HTTP request. So the two Get(…) methods are

used to get a collection of values and to get a single value given its ID. The Post(…) and

Put(…) are used to insert and modify the Value resource, while the Delete(…) method is used

to delete a resource given the ID.

As you can see, the five methods are the actions that are called against a GET, POST, PUT, or

DELETE HTTP request.

We will go further into conventions and other details about the previous code in the next

chapters. For now we will focus on the overview of an ASP.NET Web API project.

Like an ASP.NET MVC web application, Web API projects use a routing system. The

configuration of the routes is in a file called WebApiConfig.cs in the App_Start folder. Here is

the content of that file:

using System.Web.Http;

namespace HelloWebApi

{

public static class WebApiConfig

{

public static void Register(HttpConfiguration config)

{

config.Routes.MapHttpRoute(

name: "DefaultApi",

routeTemplate: "api/{controller}/{id}",

defaults: new { id = RouteParameter.Optional }

);

}

This class has one method that is invoked from the WebApiApplication class in the

global.asax. This method registers the routes needed by the application. By default, the

ValuesController defined before responds to the URI /api/Values, as we can see in the

previous code. Note that these routes, even though very similar to the ASP.NET MVC routes,

are a completely different stack. In this case, the route type is IHttpRoute and the

implementation is contained in the System.Web.Http assembly, so it’s completely new and is

not tied to System.Web.

Even if they are different, they are implemented almost in the same way: each route has a name

and a template that is tokenized to match the input patterns.

So until now, we have seen the Values controller that has the duty to manage the Values

resource and a simple routing system to route the request to the matching controller. Let’s run

the Web API application to see how it works.

剩余91页未读，继续阅读

ChrisyehGone

粉丝: 17
资源: 52

ASP.NET Web API 入门与进阶教程

asp.net_web_api_succinctly.pdf

.NET加密技术详解：Cryptography_in_.NET_Succinctly

Postgres_Succinctly.pdf

Imperative_to_functional_programming_succinctly

Nodejs_Succinctly_Node.js_Node.jsprogramming_

UnitTesting_Succinctly.pdf

2016-Delphi_Succinctly.pdf

一些很不错的JQuery的例子（附上jQuery_Succinctly.pdf）

GIS Succinctly.pdf

ASP.NET Core Succinctly

最新资源