ASP. NET Web API 2 website Newbie Learning Series navigation [continuous UPDATE]

Objective

have been on the Microsoft website to learn, website website Http://www.asp.net/web-api. Because I want to exercise the purpose of learning to read English articles, but also to learn the new technology released by Microsoft, in fact, a long time, but their rookie a, for themselves is a new technology. In view of the above two reasons, I intend to use Google Translate and Youdao dictionary, to translate this series, and through the blog Park to record their own translation learning process. Because of their own reading level is really too food, in the case of the use of tools, sometimes out of the bad statements, their own reading is uncomfortable, especially to the Web API routing of the two, so I think there are others have also translated this kind of article, after a simple search has also been translated:/http Www.cnblogs.com/r01cn/archive/2012/11/11/2765432.html, but there are many vacancies in the Great God series. So I thought about the work of the great God with his own point of smell to continue. Through the list of official website, the number of articles is indeed quite a lot, so I think, began to take a moment to learn through the Web API, as for some corner to be translated in the future to improve:

These are the list site and Google Translate.

ASP. NET WEB API series navigation

One: Getting Started (Getting started)

1.asp.net Web API 2 first lesson--Getting Started http://www.cnblogs.com/aehyok/p/3432158.html

II: Creating Web APIs (creating Web APIs)

2.asp.net Web API 2 The second lesson--crud operation Http://www.cnblogs.com/aehyok/p/3434578.html

III: Web API clients (Web API client)

3.asp.net Web API 2 Lesson Three ——. NET client invoke Web API http://www.cnblogs.com/aehyok/p/3439698.html

4.asp.net Web API 2 lesson--httpclient Message Processor http://www.cnblogs.com/aehyok/p/3442277.html

IV: Web API Routing and actions (Web API Routing and actions)

5.asp.net Web API 2 lesson--web API Routing Http://www.cnblogs.com/aehyok/p/3442051.html

6.asp.net Web API 2 Sixth lesson--web API Routing and action selection http://www.cnblogs.com/aehyok/p/3444710.html

7.asp.net Web API 2 Seventh lesson--web API exception Handling http://www.cnblogs.com/aehyok/p/3446863.html

8.asp.net Web API 2 Eighth Lesson--web attribute routing in the API http://www.cnblogs.com/aehyok/p/3449851.html

9.asp.net Web API 2 nineth lesson--create a REST API with Attribute Routing in Web API 2

V: Working with HTTP (using HTTP)

10.asp.net Web API 2 Tenth Lesson--web API HTTP Message processing

11.asp.net Web API 2 Tenth lesson--sending HTML Form Data

12.asp.net Web API 2 Tenth lesson--http Cookies in ASP Web API

VI: Formats and model binding (formatting and modeling bindings)

13.asp.net Web API 2 11th lesson--media formatters Media Formatter http://www.cnblogs.com/aehyok/p/3460164.html

14.asp.net Web API 2 11th Lesson--json and XML serialization in ASP. Web apihttp://www.cnblogs.com/aehyok/p/3460184.html

15.asp.net Web API 2 11th lesson--content negotiationhttp://www.cnblogs.com/aehyok/p/3481265.html

16.asp.net Web API 2 11th lesson--model validationhttp://www.cnblogs.com/aehyok/p/3481270.html

17.asp.net Web API 2 11th lesson--parameter Binding in ASP. NET Web apihttp://www.cnblogs.com/aehyok/p/3492259.html

VII: OData

18.asp.net Web API 2 16th lesson--creating an OData Endpoint in ASP. Web apihttp://www.cnblogs.com/aehyok/p/3545824.html

19.asp.net Web API 2 12th Lesson--supporting OData Query Options

20.asp.net Web API 2 12th Lesson--supporting OData Query Options

21.asp.net Web API 2 12th Lesson--using $select, $expand, and $value in ASP Web API OData

22.asp.net Web API 2 12th lesson--working with Entity relations in odatahttp://www.cnblogs.com/aehyok/p/3550119.html

23.asp.net Web API 2 12th lesson--supporting OData Actions in ASP. NET Web API

24.asp.net Web API 2 12th lesson--web API OData Routing conventions

25.asp.net Web API 2 12th lesson--odata Security Guidance

Eight: Security (safe)

26.asp.net Web API 2 13th lesson--authentication and Authorization in ASP.

27.asp.net Web API 2 13th Lesson--basic Authentication

28.asp.net Web API 2 13th lesson--individual Accounts in ASP Web API

29.asp.net Web API 2 13th Lesson--forms Authentication

30.asp.net Web API 2 13th lesson--integrated Windows Authentication

31.asp.net Web API 2 13th lesson--preventing cross-site Request Forgery (CSRF) Attacks

32.asp.net Web API 2 13th lesson--working with SSL in Web API

33.asp.net Web API 2 13th Lesson--external authentication Services (C #)

34.asp.net Web API 2 13th lesson--enabling Cross-origin requests in ASP.

IX: Hosting ASP (ASP. NET Web API hosting)

35.asp.net Web API 2 lesson 14th-Using Owin self-hosted web API http://www.cnblogs.com/aehyok/p/3456855.html

36.asp.net Web API 2 Lesson Nineth-Self-hosted web API http://www.cnblogs.com/aehyok/p/3456841.html

Ten: Testing and Debugging (Test and Debug)

37.asp.net Web API 2 15th lesson--tracing in ASP Web API

11: Extensibility (Extensibility)

38.asp.net Web API 2 16th Lesson--configuring ASP

39.asp.net Web API 2 16th lesson--using the Web API Dependency Resolver

12: Other resources-no plans

The above is just a list of learning, as for learning those and order no strict requirements, normal words all I will study translation, the sequence of changes may be more, this is always a difficult task, I hope I can persist. Here's a simple look at understanding the Web API.

What is the Web API?

In this article more detailed introduction of the ASP, and do not do too much emphasis here, want to know can click the link http://devproconnections.com/development/ Microsoft-aspnet-whats-new-web-api This is the original address, the great God translated address for http://www.cnblogs.com/r01cn/archive/2012/11/09/2762930.html.

The following summary excerpt from http://www.cnblogs.com/developersupport/p/aspnet-webapi.html, feeling summed up in place.

Why use the Web API

The most important thing about Web APIs is the ability to build services for a variety of clients. In addition, unlike the WCF REST service, the Web API uses various aspects of the HTTP protocol to express services (such as uri/request response header/caching/versioning/content format). Therefore, many configurations are omitted.

When you encounter these situations, you can consider using the Web API.

• Requires a Web service but does not require soap
• Need to establish non-soap-based HTTP service on the basis of existing WCF services
• Just want to publish some simple HTTP service, do not want to use the relatively complex WCF configuration
• The published service may be accessed by a bandwidth-constrained device
• Want to use the open source framework, when it is critical to debug or customize the framework

Key Features

Key features of the Web API

• Support for CRUD (create, retrieve, update, delete) operations based on HTTP verb (GET, POST, PUT, delete). The different meanings are expressed by different HTTP actions, so there is no need to expose multiple APIs to support these basic operations.
• The requested reply expresses a different meaning through the HTTP Status code, and the client can negotiate the format with the server via the accept header, such as whether you want the server to return a JSON format or an XML format.
• The requested reply format supports Json,xml and can be extended to add additional formats.
• Native support OData.
• Support for Self-host or IIS host.
• Supports most MVC features, such as Routing/controller/action Result/filter/model builder/ioc container/dependency Injection.

ASP. NET Web API and ASP. NET MVC

You might think that Web APIs are very similar to MVC, and what are the differences between them?

To point out their differences in detail,

• MVC is primarily used to build web sites that care about data as well as page presentation, while Web APIs focus only on data
• The WEB API supports format negotiation, and clients can notify the server of the desired format via the Accept header
• Web API Support Self HOST,MVC not currently supported
• The Web API expresses different actions (CRUD) through different HTTP verb, and MVC expresses the action by the action name
• The Web API is built into the ASP. Net System.Web.Http namespace, MVC is located under the System.Web.Mvc namespace, so features such as model binding/filter/routing are different
• Finally, the Web API is ideal for building mobile client Services

Web API and WCF

What is the choice between the Publishing service and the Web API and WCF? Here are a few simple rules to judge,

• If the service needs to support one-side messaging/message queue/duplex communication, select the WCF
• If the service requires tcp/named PIPES/UDP (WCF 4.5), select the WCF
• If the service needs to be on the HTTP protocol, and you want to take advantage of the various features of the HTTP protocol, select the Web API
• If the service needs to be called by various clients (especially mobile clients), select the Web API

Http://msdn.microsoft.com/en-us/library/jj823172.aspx

Summarize

A simple series of summaries and lists, which is also a very large project. For the time being, I have learned to translate six courses, and I feel that some of the knowledge points and ASP. NET MVC have relatively high similarity, which also gives me a deeper understanding of some problems in MVC. Hope to have more friends to participate in them.

ASP. NET Web API 2 website Newbie Learning Series navigation [continuous UPDATE]