Have you ever tweeted something that you would like your friends to retweet as soon as possible. I’ve seen this with new product announcements, Twitter contests, building buzz and even when applying for a social media gig. Usually the tweet includes something like “Pls RT!” With this project, I thought I’d create a retweeting engine to announce to your friends that you have a status you’d like them to retweet. This sounded like a great opportunity to deep dive into the Twitter API and OAuth within .NET application. Hence a neat side project that may have some usefulness and will definitely get us exploring some important API’s.
There are plenty of good .NET Twitter Libraries available with varying degrees of functionality. I am a huge fan of Linq so I decided to give Linq to Twitter a spin since it has high API coverage and supports oAuth out of the box.
ASP.NET MVC R3
I’ve been using the ASP.NET MVC framework since it’s first community preview several years ago and have fallen in love. It has evolved in many ways since the first CTP and I’m looking forward to experiment with some of its newest features – particularly the Razor view engine.
I believe the best way to get up to speed with an API is to jump right in and start working with it. One of the components I’m most excited to explore is the OAuth implementation for the Twitter API. With more and more services adopting the OAuth protocol, I think its safe to expect it to become the de-facto security layer for most social API’s available.
As to the other frameworks and tools involved in the project, you can expect to see the usual suspects. At this time I don’t think they’ll be a need for a database since most of the data will be coming from the Twitter API. The tools of the trade up to this point will include:
- Visual Studio 2010 Ultimate
- jQuery v1.4.4
I’m looking forward to sharing the experience step-by-step so don’t be surprised if I hit some speed bumps (or canyons) along the way. In the next part we’ll look at some preliminary solution setup and wiring some of the external libraries together. We’ll also mockup some screens and see what views and controllers it would be implying.