This sample demonstrates how to host a Windows Communication Foundation (WCF) REST service using ASP.NET routes. The Basic Resource Service sample shows a self-hosted version of this scenario and discusses the service implementation in depth. This topic focuses on the ASP.NET integration feature. For more information about ASP.NET Routing, see System.Web.Routing.
The WCF service exposes a collection of customers in a resource-oriented/REST manner. Just like a SOAP-based WCF service, the service can be hosted in ASP.NET using a .svc file. However, this is often not preferred for HTTP scenarios because it requires having .svc in the URL for the service. In addition, it requires deploying a .svc file along with the service library. These limitations can be avoided by hosting the service using ASP.NET routes, as is demonstrated in this sample.
The sample hosts the service in ASP.NET by adding a ServiceRoute in a Global.asax file. The ServiceRoute specifies the type of the service (‘Service’ in this case), the type of the service host factory to use for the service (WebServiceHostFactory in this case) and the HTTP base address for the service (‘~/Customers’ in this case).
In addition to this, the sample includes a Web.config that adds the UrlRoutingModule (to turn on ASP.NET routes) and includes the configuration for the service. In particular, the configuration configures the WCF service with a default WebHttpEndpoint that has the HelpEnabled setting to true. As a result, the WCF infrastructure creates an automatic HTML based help page at
http://localhost/Customers/help that provides information about how to construct HTTP requests to the service and how to access the service’s HTTP response – for instance, an example of how the customer details are represented in XML and JSON.
Exposing the customer collection (and more generally, any resource) in this manner allows a client to interact with a service in a uniform way using URIs and HTTP GET, PUT, DELETE and POST.
Program.cs in the Client project demonstrates how such a client can be authored using HttpWebRequest. Note that this is just one way to access a WCF service. It is also possible to access the service using other .NET Framework classes like the WCF channel factory and WebClient. Other samples in the SDK (such as the Basic HTTP Service sample and the Automatic Format Selection sample) show how to use these classes to communicate with a WCF service.
This sample consists of 3 projects:
- A Web application project that includes a WCF HTTP service hosted in ASP.NET.
- A console application project that makes calls to the service.
A shared library that contains the
Customertype used by the client and service. As the client console application runs, the client makes requests to the service and writes the pertinent information from the responses to the console window.
To use this sample
Open the solution for the ASP.NET Routes Integration sample in Visual Studio 2012.
Press CTRL+SHIFT+B to build the solution.
If it is not already open, press “CTRL+W, S” to open the Solution Explorer window.
From the Solution Explorer windows, right-click the Service project and place the cursor over the Debug context menu option so that the Start New Instance context menu appears and select Start New Instance. This launches the ASP.NET development server, which hosts the service.
From the Solution Explorer windows, right-click the Client project and place the cursor over the Debug context menu option so that the Start New Instance context menu appears and select Start New Instance.
The client console window appears and provides the URI of the running service and the URI of the HTML help page for the running service. At any point in time you can view the HTML help page by typing the URI of the help page in a browser. As the sample runs, the client writes the status of the current activity.
Press any key to terminate the client console application.
Press Shift+F5 to stop debugging the service and in the Windows Notification Area, right-click the ASP.NET development server icon and select Stop from the context menu.
The samples may already be installed on your machine. Check for the following (default) directory before continuing.