Why am I writing against the Twitter API directly?

Tuesday, March 24, 2009

Yeah, so some of my friends asked me why I am not using a twitter library instead of calling the api directly. Yeah, I'm wondering that to. Seriously, the reason why I am doing that is that .net libraries to call out to twitter that I tried under VS 2008, did not work with Windows Azure. These libraries seemed to generate a security exception. Given azure's security requirements being a little more than regular asp.net, I decided to just drop the search for a library and make my calls on my own. Not sure if its a good decision or not, but its what I did.

Original Url: http://morewally.com/cs/blogs/wallym/archive/2009/03/18/why-am-i-writing-against-the-twitter-api-directly.aspx

PS. I hear that Full Trust and Native Code support are coming to Azure.

as soon as security exception is launched, i hope this will not be good approach all the times.

ziaahmedshaikh - Wednesday, March 25, 2009 1:30:52 AM

Full Trust and Native Code support are already in Windows Azure. Just set enableNativeCodeExecution="true" in your .csdef file.

Steve Marx - Wednesday, April 1, 2009 5:10:02 PM

2 Comments