Quickstart: Create a ASP.NET Web App with Redis Cache


This quickstart shows how to create and deploy an ASP.NET web application to Azure App Service using Visual Studio 2017. The sample application connects to an Azure Redis Cache to store and retrieve data from the cache. When you complete the quickstart you have a running web app, hosted in Azure, that reads and writes to an Azure Redis Cache.

Simple test completed Azure

If you don't have an Azure subscription, create a free account before you begin.


To complete the quickstart, you must have the following prerequisites:

  • Install Visual Studio 2017 with the following workloads:
    • ASP.NET and web development
    • Azure Development

Create the Visual Studio project

Open Visual Studio and click File, New, Project.

Create project

In the New Project dialog, take the following steps:

  1. Expand the Visual C# node in the Templates list
  2. Select Cloud
  3. Click ASP.NET Web Application
  4. Ensure that .NET Framework 4.5.2 or higher is selected
  5. Give the project a name in the Name textbox, for this example we've used ContosoTeamStats
  6. Click OK.

You will be presented with a New ASP.NET Web Application screen:

Select project template

Select MVC as the project type.

Ensure that No Authentication is specified for the Authentication settings. Depending on your version of Visual Studio, the default may be set to something else. To change it, click Change Authentication and select No Authentication.

Click OK to create the project.

Create a cache

Next, you create the cache for the app.

To create a cache, first sign in to the Azure portal, and click Create a resource > Databases > Redis Cache.

New cache

In New Redis Cache, configure the settings for your new cache.

Setting Suggested value Description
DNS name Globally unique name The cache name must be a string between 1 and 63 characters and contain only numbers, letters, and the - character. The cache name cannot start or end with the - character, and consecutive - characters are not valid.
Subscription Your subscription The subscription under which this new Azure Redis Cache is created.
Resource Group TestResources Name for the new resource group in which to create your cache. By putting all the resources for an app in a group, you can manage them together. For example, deleting the resource group would delete all resources associated with the app.
Location East US Choose a region near to other services that will use your cache.
Pricing tier Basic C0 (250 MB Cache) The pricing tier determines the size, performance, and features available for the cache. For more information, see Azure Redis Cache Overview.
Pin to dashboard Selected Click pin the new cache to your dashboard making it easy to find.

Create cache

Once the new cache settings are configured, click Create.

It can take a few minutes for the cache to be created. To check the status, you can monitor the progress on the dashboard. After the cache has been created, your new cache has a Running status and is ready for use.

Cache created

Retrieve host name, ports, and access keys using the Azure Portal

When connecting to an Azure Redis Cache instance, cache clients need the host name, ports, and a key for the cache. Some clients may refer to these items by slightly different names. You can retrieve this information in the Azure portal.

To retrieve the access keys using the Azure portal, browse to your cache and click Access keys.

Redis cache keys

To retrieve host name, ports, click Properties.

Redis cache properties

Create a file on your computer named CacheSecrets.config and place it in a location where it won't be checked in with the source code of your sample application. For this quickstart, the CacheSecrets.config file is located here, C:\AppSecrets\CacheSecrets.config.

Edit the CacheSecrets.config file and add the following contents:

    <add key="CacheConnection" value="<cache-name>.redis.cache.windows.net,abortConnect=false,ssl=true,password=<access-key>"/>

Replace <cache-name> with your cache host name.

Replace <access-key> with the primary key for your cache.


The secondary access key is used during key rotation as an alternate key while you regenerate the primary access key.

Save the file.

Update the MVC application

In this section, you update the application to support a new view that will display a simple test against an Azure Redis Cache.

Update the web.config file with an app setting for the cache

When you run the application locally, the information in CacheSecrets.config is used to connect to your Azure Redis Cache instance. Later you'll deploy this application to Azure. At that time, you will configure an app setting in Azure that the application will use to retrieve the cache connection information instead of this file. Since CacheSecrets.config is not deployed to Azure with your application, you only use it while testing the application locally. You want to keep this information as secure as possible to prevent malicious access to your cache data.

In Solution Explorer, double-click the web.config file to open it.


In the web.config file, find the <appSetting> element, and add the following file attribute. If you used a different file name or location, substitute those values for the ones shown in the example.

  • Before: <appSettings>
  • After: <appSettings file="C:\AppSecrets\CacheSecrets.config">

The ASP.NET runtime merges the contents of the external file with the markup in the <appSettings> element. The runtime ignores the file attribute if the specified file cannot be found. Your secrets (the connection string to your cache) are not included as part of the source code for the application. When you deploy your web app to Azure, the CacheSecrests.config file won't be deployed.

Configure the application to use StackExchange.Redis

To configure the app to use the StackExchange.Redis NuGet package for Visual Studio, click Tools > NuGet Package Manager > Package Manager Console.

Run the following command from the Package Manager Console window:

Install-Package StackExchange.Redis

The NuGet package downloads and adds the required assembly references for your client application to access Azure Redis Cache with the StackExchange.Redis cache client. If you prefer to use a strong-named version of the StackExchange.Redis client library, install the StackExchange.Redis.StrongName package.

Update the HomeController and Layout

In Solution Explorer, expand the Controllers folder, and open the HomeController.cs file.

Add the following two using statements at the top of the file to support the cache client and app settings.

using System.Configuration;
using StackExchange.Redis;

Add the following method to the HomeController class to support a new RedisCache action that executes some commands against the new cache.

    public ActionResult RedisCache()
        ViewBag.Message = "A simple example with Azure Redis Cache on ASP.NET.";

        var lazyConnection = new Lazy<ConnectionMultiplexer>(() =>
            string cacheConnection = ConfigurationManager.AppSettings["CacheConnection"].ToString();
            return ConnectionMultiplexer.Connect(cacheConnection);

        // Connection refers to a property that returns a ConnectionMultiplexer
        // as shown in the previous example.
        IDatabase cache = lazyConnection.Value.GetDatabase();

        // Perform cache operations using the cache object...

        // Simple PING command
        ViewBag.command1 = "PING";
        ViewBag.command1Result = cache.Execute(ViewBag.command1).ToString();

        // Simple get and put of integral data types into the cache
        ViewBag.command2 = "GET Message";
        ViewBag.command2Result = cache.StringGet("Message").ToString();

        ViewBag.command3 = "SET Message \"Hello! The cache is working from ASP.NET!\"";
        ViewBag.command3Result = cache.StringSet("Message", "Hello! The cache is working from ASP.NET!").ToString();

        // Demostrate "SET Message" executed as expected...
        ViewBag.command4 = "GET Message";
        ViewBag.command4Result = cache.StringGet("Message").ToString();

        // Get the client list, useful to see if connection list is growing...
        ViewBag.command5 = "CLIENT LIST";
        ViewBag.command5Result = cache.Execute("CLIENT", "LIST").ToString().Replace(" id=", "\rid=");


        return View();

In Solution Explorer, expand Views>Shared folder, and open the _Layout.cshtml file.


@Html.ActionLink("Application name", "Index", "Home", new { area = "" }, new { @class = "navbar-brand" })


@Html.ActionLink("Azure Redis Cache Test", "RedisCache", "Home", new { area = "" }, new { @class = "navbar-brand" })

Add a new RedisCache view

In Solution Explorer, expand the Views folder, and then right-click the Home folder. Choose Add > View....

In the Add View dialog, enter RedisCache for the View Name, and click Add.

Replace the code in the RedisCache.cshtml file with the following code:

    ViewBag.Title = "Azure Redis Cache Test";

<br /><br />
<table border="1" cellpadding="10">

Run the app locally

By default the project is configured to host the app locally in IIS Express for testing and debugging.

In Visual Studio on the menu, click Debug > Start Debugging to build and start the app locally for testing and debugging.

In the browser, click Azure Redis Cache Test on the navigation bar.

In the example below, you can see the Message key previously had a cached value, which was set using the Redis Console in the portal. The app updated that cached value. The app also executed the PING and CLIENT LIST commands.

Simple test completed local

Publish and run in Azure

Once you have successfully tested the app locally, you will deploy the app to Azure and run it in the cloud.

Publish the app to Azure

In Visual Studio, right-click the project node in Solution Explorer, and choose Publish.


Click Microsoft Azure App Service, choose Create New, and click Publish.

Publish to app service

In the Create App Service dialog, make the following changes:

Setting Recommended Value Description
App Name Use default The app name will be the host name for the app when deployed to Azure. The name may have a timestamp suffix added to it if necessary to make it unique.
Subscription Choose your Azure subscription This subscription will be charged for any related hosting charges. If you have multiple Azure subscriptions, Verify the desired subscription is selected.
Resource Group Use the same resource group where you created the cache. For example, TestResourceGroup. The resource group helps you want to manage all resources as a group. Later when you want to delete the app, you can just delete the group.
App Service Plan Click New and create a new App Service Plan named TestingPlan.
Use the same Location you used when creating your cache.
Choose Free for the size.
An App Service plan defines a set of compute resources for a web app to run with.

App Service Dialog

Once you have the App Service hosting settings configured, click Create to create a new App Service for your app.

Monitor the Output window in Visual Studio to see the status of the publish to Azure. When publishing has successfully completed, the URL for the App Service is logged as shown below:

Publishing Output

Add the app setting for the cache

Once publishing has completed for the new App Service, add a new app setting. This setting will be used to store the cache connection information. Type the app name in the search bar at the top of the Azure portal to find the new App Service you just created.

Find App Service

Add a new app setting named CacheConnection for the app to use to connect to the cache. Use the same value you configured for CacheConnection in your CacheSecrets.config file. The value contains the cache host name and access key.

Add App Setting

Run the app in Azure

In your browser, browse to the URL for the App Service. The URL is shown in the results of the publishing operation in the Output window in Visual Studio. It is also provided in the Azure portal on the Overview page of the App Service you created.

Click Azure Redis Cache Test on the navigation bar to test cache access.

Simple test completed Azure

Clean up resources

If you will be continuing to the next tutorial, you can keep the resources created in this quickstart and reuse them.

Otherwise, if you are finished with the quickstart sample application, you can delete the Azure resources created in this quickstart to avoid charges.


Deleting a resource group is irreversible and that the resource group and all the resources in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources. If you created the resources for hosting this sample inside an existing resource group that contains resources you want to keep, you can delete each resource individually from their respective blades instead of deleting the resource group.

Sign in to the Azure portal and click Resource groups.

In the Filter by name... textbox, type the name of your resource group. The instructions for this article used a resource group named TestResources. On your resource group in the result list, click ... then Delete resource group.


You will be asked to confirm the deletion of the resource group. Type the name of your resource group to confirm, and click Delete.

After a few moments, the resource group and all of its contained resources are deleted.

Next steps

In this next tutorial, you will use Azure Redis Cache in a more real-world scenario to improve performance of an app. You will update this application to cache leaderboard results using the cache-aside pattern with ASP.NET and a database.