Geeks With Blogs
Joe Mayo

Today, I released the latest version of LINQ to Twitter, v2.1.04. Many of the modifications include new parameters for commands and queries, or new Entity properties. A few items were deprecated, so look for Obsolete warnings and minor changes to overloads. i.e. Since Twitter automatically wraps all links with URLs, the WrapLinks parameter is deprecated.

Some notable changes occurred in the areas of authentication where there was a bug fix to WinRtAuthorizer, basic streams use OAuth, and I added a new ApplicationOnlyAuthorizer:

WinRtAuthorizer Bug Fix – There was a race condition with the async implementation of AuthorizeAsync on the WinRtAuthorizer. This is now fixed and, if you’re using WinRtAuthorizer, you’ll want to upgrade to upgrade your version of LINQ to Twitter if you’re using v2.1.03 or earlier.

OAuth in Basic Streams – User streams and Site streams already use OAuth, but the Basic streams such as Filter, Sample, and Firehose were originally implemented with username/password authentication. Twitter API v1.1 requires OAuth on all streams, so I removed the capability to perform username/password authentication and implemented OAuth. Since Twitter API v1.0 will be deprecated within weeks, you’ll  want to upgrade to ensure your streams keep working.

ApplicationOnlyAuthorizer – This is a new authorizer in LINQ to Twitter. On Mar 11, Twitter announced Application-only authentication. Within hours, I had implemented and checked it into LINQ to Twitter. This authorizer, as it’s name implies, is intended for non-user scenarios. A user is someone who logs on, tweets, or performs some other action on their own behalf. However, an application can run in stand-alone mode on the server as a scheduled job, service, or worker-role, which would be a good choice for application-only authorization.

Finally, I want to give a shout-out to a few people who contributed code to this release: Greg Ennis and Ayo Adesugba. They both submitted pull requests. There were also people who submitted new issues that either describe a problem in detail with a recommended solution or provided the code to fix a problem, in the Issues area of the LINQ to Twitter site on



LINQ to Twitter v2.1.04 via

LINQ to Twitter v2.1.04 via NuGet



Posted on Friday, March 15, 2013 8:40 AM | Back to top

Copyright © Joe Mayo | Powered by: