Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am new to ASP.Net MVC and ASP.Net web api.
I have worked on Web services and cosuming them.
But I am not sure how to host ASP.Net web api and consume the same from another ASP.Net MVC application. I found some samples where people are using the api from the same project. In real world I really doubt the usage would be limited to one project.
Can some body please post some examples or links which can explain the same?
Hosting ASP.NET Web API in an MVC web application makes perfect real world sense if you are mostly using the API to make AJAX type calls from your web client. Having the API and web application in the same project eliminates issues with cross-domain Ajax calls, which requires JSONP. But ASP.NET Web API can easily support JSONP if needed with a custom formatter like JsonMediaTypeFormatter available from WebApiContrib.
ASP.NET Web API makes developing REST API’s easy. You use the same conventions as developing a controller in MVC. To create it separate from your web application just create an MVC 4 project and create your controllers using an ApiController instead of the standard Controller for rendering Views. Then just deploy your application just like any web application to IIS (you can also self-host ASP.NET Web API’s in something like a Windows Service). Here is an example on the official ASP.NET Web API website that calls a REST API developed in ASP.NET Web API from a console application. There are many more examples on this site.