Practical tutorials on operating ASP.NET Web API

---

Overview

REST (Representational State Transfer) has been increasingly discussed about REST API, and Microsoft has also added Web API functionality to ASP.NET.

We just took a look at the use of Web API and see if the current version has solved this problem.

Project creation

After installing Visual Studio 2012, we click New Project->Installed Template->Web->ASP.NET MVC 4 Web Application to create a new project.

Project Template Select Web API.

In the Model we still add the User class used in the previous article.

1 namespace WebAPI.Models
2 {
public class Users
4​ public
int UserID {get; set; } 6
7       public
string UserName { get; set; } 8
9     public
string UserEmail { get; set; } 10 }
11 }

Modify the automatically generated ValueController to Users Controller.

GET data

Use the HTTP get method to request data. The entire Web API request processing is based on the MVC framework.

The code is as follows.

 1 using System;
 2 using System.Collections.Generic;
 3 using System.Linq;
 4 using System.Net;
 5 using System.Net.Http;
 6 using System.Web.Http;
 7 using WebAPI.Models;
 8 
 9 namespace WebAPI.Controllers
10 {
11     public class UsersController : ApiController
12     {
13         /// 

14         /// User Data List
15         /// 

16         private readonly List _userList = new List
17         {
18             new Users {UserID = 1, UserName = "Superman", UserEmail = "Superman@cnblogs.com"},
19             new Users {UserID = 2, UserName = "Spiderman", UserEmail = "Spiderman@cnblogs.com"},
20             new Users {UserID = 3, UserName = "Batman", UserEmail = "Batman@cnblogs.com"}
21         };
22 
23         // GET api/Users
24         public IEnumerable Get()
25         {
26             return _userList;
27         }
28 
29         // GET api/Users/5
30         public Users GetUserByID(int id)
31         {
32             var user = _userList.FirstOrDefault(users => users.UserID == id);
33             if (user == null)
34             {
35                 throw new HttpResponseException(HttpStatusCode.NotFound);
36             }
37             return user;
38         }
39 
40         //GET api/Users/?username=xx
41         public IEnumerable GetUserByName(string userName)
42         {
43             return _userList.Where(p => string.Equals(p.UserName, userName, StringComparison.OrdinalIgnoreCase));
44         }
45     }
46 }

Constructed a user list and implemented three methods. Let’s make the request below.

When using different browsers to request, you will find that the returned format is different.

Using Chrome request first, we found that the Content-Type in the HTTP Header is xml type.

We change the FireFox request again and find that the Content-Type is still xml type.

We used IE to request again and found that this is the case.

Open the saved file and we find that the requested data is in JSON format.

The reason for this difference is that the Content-Type in the Request Header sent by different browsers is inconsistent.

We can use Fiddler to verify it.

Content-Type: text/json

Content-Type: text/xml

POST data

implements a function added by User, and the accepted type is User entity. The data of our POST is the corresponding JSON data to see if the problems encountered by dudu in the Beta version have been solved.

1 //POST api/Users/Users Entity Json
2 public Users Add([FromBody]Users users)
3 {
4 if (users = = null)
5                                                                                                                                              ​​
return users;10}


We still use Fiddler to simulate POST data. Before making the POST request, we first attach the code to the process and set a breakpoint at the Add method.
In Visual Studio 2012, the debug HOST program becomes IIS Express. We use Ctrl+ALT+P to attach to its process. Use Fiddler to simulate POST below. Note that the Content-Type in the Request Header is text/json, and the json content of the POST is: 1 {"UserID":4,"UserName":"Parry","UserEmail":Parry@cnblogs. com}

After clicking Execute, it jumps to the breakpoint we set earlier. Let’s take a look at the submitted data.

In this way, the problems dudu encountered in Beta have been solved.

Conclusion

The ASP.NET framework has developed along the way, and its functions are indeed becoming more and more powerful and convenient. I hope we can abandon the language debate and return to pure technical discussions. Everyone says that Microsoft's technology changes too fast. What is the nature of the change? Is it good to remain unchanged?

In the second part, we will take a look at some security verification issues in Web API.

If there are any errors, please point them out and discuss them.

If you like it, giving it a recommendation is the best affirmation for the article. :)

The above is the detailed content of Practical tutorials on operating ASP.NET Web API. For more information, please follow other related articles on the PHP Chinese website!