IHttpActionResult vs HttpResponseMessage

Video ready, click here to close ×

Text version of the video


All ASP .NET Web API Text Articles and Slides

All ASP .NET Web API Videos

Video ready, click here to close ×

All Dot Net and SQL Server Tutorials in English

All Dot Net and SQL Server Tutorials in Arabic

In Web API 1, we have HttpResponseMessage type that a controller action method returns. A new type called “IHttpActionResult” is introduced in Web API 2 that can be returned from a controller action method. Instead of returning HttpResponseMessage from a controller action, we can now return IHttpActionResult. There are 2 main advantages of using the IHttpActionResult interface.

1. The code is cleaner and easier to read
2. Unit testing controller action methods is much simpler. We will discuss, how easy it is to unit test a method that returns IHttpActionResult instead of HttpResponseMessagein a later video.

Consider the following StudentsController. Notice both the Get() methods return HttpResponseMessage. To create the HttpResponseMessage, we either use CreateResponse() or CreateErrorResponse() methods of the Request object.

public class StudentsController : ApiController
static List[Student] students = new List[Student]()
new Student() { Id = 1, Name = “Tom” },
new Student() { Id = 2, Name = “Sam” },
new Student() { Id = 3, Name = “John” }

public HttpResponseMessage Get()
return Request.CreateResponse(students);

public HttpResponseMessage Get(int id)
var student = students.FirstOrDefault(s =] s.Id…



Leave a Reply

Your email address will not be published. Required fields are marked *