Shulou(Shulou.com)06/03 Report--

This article mainly explains "how to create a complete ASP.NET Web API project". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn how to create a complete ASP.NET Web API project.

Visual Studio provides us with a project template specifically for creating ASP.NET Web API applications, and with the help of the wizard provided by this project template, we can create a complete ASP.NET Web API project "with one click". During the project creation process, Visual Studio will automatically add the necessary assembly references and configurations for us, and even automatically generate the relevant code for us. In a word: the project generated by the wizard is an executable application itself after it is created.

First, create a Web API project through VS2013 and .NET 4.5.1

1. Create a new project under the solution

2. Select the project WEB API template. The MVC at the bottom mainly comes with Microsoft API Helper by default and publishes using MVC.

3. Safety selection

4. Click the OK button and VS2013 will generate a simple Web API project.

5. Run the project. After starting the project, click the API button on the interface to see the API created by default.

6. Create a new Products API

(1) add ProductController

(2) Select empty controller

(3) implement API in ProductController

[RoutePrefix ("api/products")] public class ProductController: ApiController {/ / get product paging API: api/products/product/getList [HttpGet, Route ("product/getList")] public Page GetProductList () {throw new NotImplementedException ();} / / get a single product API: api/products/product/get?productId= product ID [HttpGet, Route ("product/get")] public Product GetProduct (Guid productId) {throw new NotImplementedException () } / / Product New API: api/products/product/add?productId= Product ID [HttpPost, Route ("product/add")] public Guid AddProduct (Product product) {throw new NotImplementedException ();} / / Product add API: api/products/product/add?productId= Product ID [HttpPost, Route ("product/update")] public void UpdateProduct (Guid productId, Product product) {throw new NotImplementedException () } / / Product deletion API: api/products/product/delete?productId= product ID [HttpDelete, Route ("product/delete")] public void DeleteProduct (Guid productId) {throw new NotImplementedException ();}}

II. ASP.NET Web API characteristics

1. Advanced HTTP programming model

Use the new strongly typed HTTP object model to directly manipulate HTTP requests and responses, using the same programming model and HTTP pipeline on HTTP clients

2. Support routing

Web API fully supports ASP.NET routing, including routing parameters and constraints. In addition, mapping to actions supports conventions so that you no longer need to add attributes such as [HttpPost] to a class or method.

3. Content negotiation

The client and the server can work together to determine the format of the data returned by API. XML, JSON and Form URL-Encoded formats are supported by default, which can be extended to add custom formats or even replace the default content negotiation policy

4. Model binding and verification

The model binder can easily extract data from HTTP requests and convert them into .net objects used in action methods.

5. Filtering

Web API supports filtering, including the well-known [Authorize] filtering tags, custom filtering can be added and inserted for Action, authentication, exception handling, etc.

6. Query aggregation

As long as Iqueryable is simply returned, Web API will support querying through the OData address convention

7. Improved Http detail testability

Instead of setting HTTP details on a static Context object, Web API uses HttpRequestMessage and HttpResponseMessage instances, and you can add custom types to these Http types using generic versions of these objects

8. Improved dependency inversion (IoC) support

Web API uses the service locator pattern implemented by MVC Dependency Resolver to obtain instances in different scenarios

9. Code-based configuration

Web API uses separate code to complete the configuration, thus ensuring the cleanliness of the configuration file

10. Self-hosting (Self-Host)

In addition to being hosted in IIS, Web API can also be hosted in processes, and routing and other features can still be used.

Thank you for your reading, the above is the content of "how to create a complete ASP.NET Web API project". After the study of this article, I believe you have a deeper understanding of how to create a complete ASP.NET Web API project. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.