asp.net-web-api Getting started with asp.net-web-api

Help us to keep this website almost Ad Free! It takes only 10 seconds of your time:
> Step 1: Go view our video on YouTube: EF Core Bulk Extensions
> Step 2: And Like the video. BONUS: You can also share it!

Remarks

This section provides an overview of what asp.net-web-api is, and why a developer might want to use it.

It should also mention any large subjects within asp.net-web-api, and link out to the related topics. Since the Documentation for asp.net-web-api is new, you may need to create initial versions of those related topics.

Installation or Setup

Detailed instructions on getting asp.net-web-api set up or installed.

To add Web API to an existing MVC application.

Use Nuget to find the Web Api Package.

You can do that either by using the Manage Nuget Packages and searching for the Web Api package or use Nuget Package Manager and type

PM> Install-Package Microsoft.AspNet.WebApi
 

Add WebApiConfig.cs to the App_Start/ folder The config file should contain this.

using System.Web.Http;
namespace WebApplication1
{
public class WebApiApplication : System.Web.HttpApplication
{
    protected void Application_Start()
    {
        GlobalConfiguration.Configure(config =>
        {
            config.MapHttpAttributeRoutes();

            config.Routes.MapHttpRoute(
                name: "DefaultApi",
                routeTemplate: "api/{controller}/{id}",
                defaults: new { id = RouteParameter.Optional }
            );
        });
    }
 }
}
 

Source : Configuring ASP.NET Web API

Add GlobalConfiguration.Configure(WebApiConfig.Register); in Application_Start of the Global.asax file.

What and Why ASP.NET Web API ?

What? : A fully supported and extensible framework for building HTTP based endpoints. In the world of HTML5, mobile devices, and modern development techniques HTTP have become the default option for building rich, scalable services. The ASP.NET Web API provides an easy to use set of default options but also provides a deep extensibility infrastructure to meet the demands of any scenario using HTTP.

Why? :

  • An HTML5 application that needs a services layer.
  • A mobile application that needs a services layer.
  • A client-server desktop application that needs a services layer.


Got any asp.net-web-api Question?