In-Role Cache Release Notes - October 2012 (Windows Azure Cache)
This topic contains the release notes for Windows Azure Cache specific to the October 2012 release of the Windows Azure SDK. For the latest Windows Azure release notes, see Windows Azure Release Notes.
For other questions about Cache, see In-Role Cache FAQ (Windows Azure Cache).
Windows Azure Caching (Preview) is now Released
Cache hosted on Windows Azure roles is now released and supported in production scenarios. For more information, see About In-Role Cache for Windows Azure Cache.
Windows Azure Caching development and Server AppFabric development should not be done on the same machine
It is not supported to develop Windows Azure cloud services that use Cache on a machine that also has Microsoft AppFabric 1.1 for Windows Server. You might see unexpected or inconsistent Cache behavior when running either your AppFabric application on the machine or when testing the Windows 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 Cache. Instead of multiple cache clusters, make use of multiple named caches. For more information, see About In-Role Cache for Windows Azure Cache.
The NuGet package installation will fail if total path length is exceeded
Installing the Windows 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.