Geeks With Blogs

News
Joe Mayo Cloud and Glue April 2010 Entries
Modifying Service URLs with LINQ to Twitter
It’s funny that two posts so close together speak about flexibility with the LINQ to Twitter provider. There are certain things you know from experience on when to make software more flexible and when to save time. This is another one of those times when I got lucky and made the right choice up front. I’m talking about the ability to switch URLs. It only makes sense that Twitter should begin versioning their API as it matures. In fact, most of the entire API has moved to the v1 URL at “https://api.twitter.com/1/”, ......

Posted On Thursday, April 22, 2010 9:11 PM

Twitter User/Search Feature Header Support in LINQ to Twitter
LINQ to Twitter’s goal is to support the entire Twitter API. So, if you see a new feature pop-up, it will be in-queue for inclusion. The same holds for the new X-Feature… response headers for User/Search requests. However, you don’t have to wait for a special property on the TwitterContext to access these headers, you can just use them via the TwitterContext.ResponseHeaders collection. The following code demonstrates how to access the new X-Feature… headers with LINQ to Twitter: var user = (from ......

Posted On Friday, April 16, 2010 2:32 PM

Using LINQ Distinct: With an Example on ASP.NET MVC SelectListItem
One of the things that might be surprising in the LINQ Distinct standard query operator is that it doesn’t automatically work properly on custom classes. There are reasons for this, which I’ll explain shortly. The example I’ll use in this post focuses on pulling a unique list of names to load into a drop-down list. I’ll explain the sample application, show you typical first shot at Distinct, explain why it won’t work as you expect, and then demonstrate a solution to make Distinct work with any custom ......

Posted On Wednesday, April 7, 2010 5:55 PM

Comments on Comments
I almost tweeted a reply to Capar Kleijne's question about comments on Twitter, but realized that my opinion exceeded 140 characters. The following is based upon my experience with extremes and approaches that I find useful in code comments. There are a couple extremes that I've seen and reasons why people go the distance in each approach. The most common extreme is no comments in the code at all. A few bad reasons why this happens is because a developer is in a hurry, sloppy, or is interested in ......

Posted On Thursday, April 1, 2010 11:17 AM

Copyright © Joe Mayo | Powered by: GeeksWithBlogs.net | Join free