Unanswered cacheName attribute is not allowed

  • Saturday, April 28, 2012 5:26 PM
     
     

    I try to use Windows Azure App Fabric caching services

    I have configured Azure caching, add references to VisualStudio MVC project and configured web.config with Client Configuration downloaded from Azure caching service.

    My sessionState web.config section is:

        <sessionState mode="Custom" customProvider="AppFabricCacheSessionStoreProvider">
          <providers>
            <add name="AppFabricCacheSessionStoreProvider"
                 type="Microsoft.Web.DistributedCache.DistributedCacheSessionStateStoreProvider, Microsoft.Web.DistributedCache"
                 cacheName="default"
                 useBlobMode="true"
                 dataCacheClientName="default"
            />
          </providers>

    </sessionState> 

    In VisualStudio I receive web.config warning: The 'cacheName' attribute is not allowed. Also, same massage is for two additional atributes (useBlobMode, dataCacheClientName)

    Any suggestions?

    Thanks

All Replies

  • Monday, April 30, 2012 6:12 AM
     
     

    Hi CarperX,

      You are getting this warning because you are using customProvider and these tags are not part of default session state provider tags. This applies for tags of any other custom provider as well. You can go ahead and deploy your project. It would work fine.

    Thanks,

    Alfan T P

  • Monday, April 30, 2012 6:26 AM
     
     

    Hi,

    If you have all the windows  azure app fabric caching libraries referenced the above mentioned warning won't create any issues. You can ignore these warnings and proceed.

    Thanks

    Arun


    arunks

  • Wednesday, May 02, 2012 12:15 AM
     
     

    Hi!

    I have referenced all required libraries and I was following documentation and client configuration from Azure app fabric.

    I could not test this configuration in emulator?

    How to resolve this?

    Thanks

  • Monday, May 14, 2012 11:17 AM
     
     
    After adding the reference to Microsoft.Web.DistributedCache, my problem got resolved.