Share via

Azure In-Role Cache Release Notes - October 2012


Microsoft recommends all new developments use Azure Redis Cache. For current documentation and guidance on choosing an Azure Cache offering, see Which Azure Cache offering is right for me?

This topic contains the release notes for Microsoft Azure Cache specific to the SDK. For the latest Azure release notes, see Azure Release Notes.

For other questions about caching, see Azure In-Role Cache FAQ.

In-Role Cache is Generally Available

In-Role Cache is now Generally Available and supported in production scenarios. For more information, see About In-Role Cache for Azure Cache.

In-Role Cache development and Server AppFabric development should not be done on the same machine

It is not supported to develop Azure cloud services that use caching on a machine that also has Microsoft AppFabric 1.1 for Windows Server. You might see unexpected or inconsistent caching behavior when running either your AppFabric application on the machine or when testing the Azure application in the compute emulator. Use separate computers for developing these applications and install only the required files.

Only one cache cluster is supported in a cloud service

Each cloud service should only configure one cache cluster. Specifically, this means that only one role per cloud service should enable caching. Instead of multiple cache clusters, make use of multiple named caches. For more information, see About In-Role Cache for Azure Cache.

The NuGet package installation will fail if total path length is exceeded

Installing the Microsoft Azure Cache libraries via NuGet might fail with the following error.

Install failed. Rolling back...
The specified path, file name, or both are too long.

This can happen if the path where your project is located is too long. We recommend that you move your project to another location with a shorter path. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.