exactly and my cache is working as expected I am able to store and retrieve data so why has the achievement not shown up? The azure account I am connecting to is my companies and has been around for a while. I'm assuming there is something in VS that should be triggering this but it is not. Thanks.
Any idea what's going on here? Thanks.
For $20.000,- I will grant you the "Show me the cash" achievement!
Kidding aside, no idea what is going on.
It's looking for some sort of marker that you used Azure Cache.
node look like?
PS - You are very close to getting them all!
This is in my web.config of a Azure WCF Service Project.
DataCacheFactory cacheFactory = new DataCacheFactory();
DataCache cache = cacheFactory.GetDefaultCache();
var r = (string)cache.Get("item");
Also this is the last achievement i need to have them all so please help. Thanks so much.
I'm trying to get this one too...
@karstenj Any suggestions? Thanks.
I see the problem. One thing that we look for in that achievement is the name of the host, which used to always be *.vo.msecnd.net. Since we built this achievement, it appears that the DNS named has changed to *.cache.windows.net.
So we're going to need to update the extension. Until then, you can prob figure out a workaround BTW, congrats on getting all the achievements. You truly are an ace hack.
@karstenj when is the next version comming out. I can't workaround the issues with a simple host file spoof or anything of that nature because of acs security. I'm really anxious to get this one since it's my last. Thanks.
@AceHack: just use the faulty adres, get the achievement, put the adres back, done!
no need to wait for update
@maddus I did that and it did not work. So I tried updating my hosts file to hasve the address point to the right ip address and still no luck. I'm assuming it needs to be a successful call or something.
@AceHack: it checks them compile time, did you try and compile the solution?
@maddus yes I did, recompile too and running the app.
Okay, version 2.1 of the achievements extension fixes this!
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.