2012年7月30日 下午 02:34
I have an Azure Application with Private Cache. On my dev machine I have an AppFabric 1.1 installation. I dropped Windows Azure Caching Preview from NuGet, and did settings in web.config whoose uses my local cache instqance (via <hosts />), and a web.release.config for Azure (via <autoDiscover/>).
But it is not working since DLLs from Windows Azure Caching Preview are not good for AF 1.1, and DLLs from AF 1.1 are not good for Azure.
Does anyone know a good solution for this. I wanna debug my caching code also u no.
2012年7月31日 上午 05:39版主
I'd suggest you confirm it with our Azure support team.
Please refer to https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn.
In the subsequent page, please select "Other".
Hope this helps.
2012年7月31日 上午 06:19
Azure cache preview client and AppFabric 1.1 installation don't work together on the same box. On your dev box, do you test your app with dev fabric? If yes, you should be able to just run the cache role as well and debug the client with the cache preview binaries brought down by nuget. Let us know if you're facing issues doing that.
2012年7月31日 上午 06:24
We have a Web Role Accelerator based solution so I don't test it with dev fabric, it's a regular IIS website in my debug environment. Ok, I'm tring to have a debug configuration using dev fabric.
Thanks for the info.
2012年8月8日 下午 11:54
What are the options if I can't use emulator? Instead I am working directly with asp.net mvc web sites in development setting.
2012年8月9日 上午 06:57
AF 1.1 cache dlls are not compatible with Dedicated azure cache dlls.
Would like to understand your scenario better ... Is it like you've a single application which you want to run against AppFabric Cache Cluster in On-Premise and also run it in Azure against Azure cache ?
You can debug your application in devfabric using Azure Caching (Preview) bits as it'll start the service locally and you can do all your get/put operations as you wish.
2012年8月9日 上午 07:35
Yes, exactly. We have a solution that needs to support Azure and OnPremises aswell. Because of different DLLs, deploying is not as easy as it could be, because we have to replace DLLs manually after deployment on the onpremise intallation.
Now I'm thinking on a MEX based solution ...