ASP.NET Caching Integration
This sample demonstrates how to utilize the ASP.NET output cache with the WCF WEB HTTP programming model. Please see the Basic Resource Service sample for a self-hosted version of this scenario that discusses the service implementation in depth. This topic focuses on the ASP.NET output cache integration feature.
Integration with the ASP.NET Output Cache
The samples may already be installed on your machine. Check for the following (default) directory before continuing.
If this directory does not exist, go to Windows Communication Foundation (WCF) and Windows Workflow Foundation (WF) Samples for .NET Framework 4 to download all Windows Communication Foundation (WCF) and WF samples. This sample is located in the following directory.
The sample uses the AspNetCacheProfileAttribute to utilize ASP.NET output caching with the Windows Communication Foundation (WCF) service. The AspNetCacheProfileAttribute is applied to service operations, and provides the name of a cache profile in a configuration file that should be applied to responses from the given operation.
In the Service.cs file of the sample Service project, both the
GetCustomers operations are marked with the AspNetCacheProfileAttribute, which provides the cache profile name "CacheFor60Seconds". In the Web.config file of the Service project, the cache profile "CacheFor60Seconds" is provided under the <
caching> element of <
system.web>. For this cache profile, the value of the
duration attribute is "60", so responses associated with this profile are cached in the ASP.NET output cache for 60 seconds. Also, for this cache profile, the
varmByParam attribute is set to "format" so requests with different values for the
format query string parameter have their responses cached separately. Lastly, the cache profile’s
varyByHeader attribute is set to "Accept", so requests with different Accept header values have their responses cached separately.
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) illustrate how to use these classes to communicate with a WCF service.
To run the sample
The sample consists of three projects:
Service: A Web Application project that includes a WCF HTTP service hosted in ASP.NET.
Client: A console application project that makes calls to the service.
Common: A shared library that contains the Customer type 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 run the sample
Open the solution for the ASP.NET Caching Integration Sample.
Press CTRL+SHIFT+B to build the solution.
If the Solution Explorer window is not already open, press CTRL+W+S.
From the Solution Explorer window, right click the Service project and select Start New Instance. This launches the ASP.NET development server, which hosts the service.
From the Solution Explorer window, right click the Client project 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.
In the Windows Notification Area, right click the ASP.NET development server icon and select Stop.