Skip to content
Twitterizer is a .NET class library that provides an easy-to-use interface for the Twitter web api. It is written for developers. It's features are easy to discover and follow a consistent design pattern.
C# ASP Other
Latest commit 90b0e7f Sep 25, 2015 @meebey meebey TwitterStatus: parse quoted tweets (fixes #92)
Thanks goes to @silviabastos
Failed to load latest commit information.
ExampleApplications Upgrade all projects to use .net framework 4 or the client profile as… Aug 13, 2011
Twitterizer.OAuth Fixed xml documentation errors. Removed unused assemblie references. Nov 22, 2012
Twitterizer2.Async.Silverlight Fixed xml documentation errors. Removed unused assemblie references. Nov 22, 2012
Twitterizer2.Async Merge branch 'master' of https://github.com/blooksa/Twitterizer into … Dec 15, 2012
Twitterizer2.Data Upgrade all projects to use .net framework 4 or the client profile as… Aug 13, 2011
Twitterizer2.Silverlight Fixed xml documentation errors. Removed unused assemblie references. Nov 22, 2012
Twitterizer2.Streaming.Silverlight Fixed xml documentation errors. Removed unused assemblie references. Nov 22, 2012
Twitterizer2.Streaming TwitterSteamEvent: support quoted_tweet for stream events Sep 25, 2015
Twitterizer2.TestCases Merge pull request #52 from sconno05/develop Jan 24, 2013
Twitterizer2 TwitterStatus: parse quoted tweets (fixes #92) Sep 25, 2015
Twitterizer2lite Removed reference to nuget target from project files. Feb 14, 2012
XML Documentation Start of documentation for mono usage. Feb 26, 2011
lib Changes for a nuget update. Nov 5, 2012
packages Update Json.4.5.7 Jul 11, 2012
.gitignore Supersized gitignore Nov 10, 2014
CommonAssemblyInfo.cs Changes for a nuget update. Nov 5, 2012
CustomDictionary.xml No commit message Mar 9, 2010
GettingStarted.txt Fixing invalid endpoint values in list command classes. Sep 4, 2010
Json.NET.license.txt No commit message May 11, 2010
NugetPackage.bat Prepping changes for nuget update. May 29, 2012
NugetPublish.bat Prepping changes for nuget update. May 29, 2012
PackageReleases.bat Re-included entities in the timelines. Nov 21, 2010
Packages.dgml Nuget fixes for externals for each project and source files so projec… Dec 13, 2011
README.md README.md: fix markup Sep 25, 2015
Twitterizer2.license.txt No commit message Mar 12, 2010
Twitterizer2.nunit Changed CommandPerformer so that it isn't generic, but the PerformAct… Jun 14, 2011
Twitterizer2.shfbproj Fixes 88 (Thanks Ian) Apr 5, 2011
Twitterizer2.sln Modifications to the solution file. The release driectory will now lo… May 29, 2012
twitterizer.FxCop No commit message May 26, 2010
twitterizer.nuspec Changes for a nuget update. Nov 5, 2012

README.md

Twitterizer

Example

var response = TwitterStatus.Update(credentials, "Twitterizer is fantastic!");
if (response.Result == Success)
{
    DisplaySuccessMessageFor(response.ResponseObject);
}
else
{
    DisplayErrorMessage(response.ErrorMessage);
}



var myFeed = TwitterTimeline.HomeTimeline(credentials);

History

Twitterizer started in May of 2008 as an excuse for me to explore design patterns, have a little fun coding, and stretch out my architectural legs. I never set out to create an open source library, much less a popular one (in the last 30 days of its life, Twitterizer.net pulled 8,560 unique visitors and nearly 52k views).

In 2009 the Smuxi project made use of the Twitterizer library to support Twitter as a built-in feature in their popular IRC client. As of 2013 Twitterizer is part of the Smuxi project umbrella and thus actively maintained. In August 2012 Smuxi ported Twitterizer to Newtonson.Json 4.5.8, in August 2013 Twitterizer was ported to the Twitter v1.1 API, in November 2013 proxy support was added to the Streaming API, and in Janary 2014 Twitterizer was ported to enforced HTTPS.

Plans for the future

Version 2.4.3

The next minor version will contain only high priority bug fixes while Version 3 is in development.

Version 3

  1. Drop support of Silverlight (unless developers come forward to own it)
  2. Twitterizer project to be async-only using the TPL
  3. Drop Twitterizer.OAuth library (let's face it, it's not a very great product) and, in fact:
  4. Evaluate relying upon an external OAuth library (DotNetOpenAuth, for example)
  5. Sync command classes and objects with Twitter's 1.1 documentation
  6. Redesign unit tests; properly mock objects and run tests using static json data
  7. Establish continuous deployment to Nuget

Contribute

  1. Create or claim an issue
  2. Fork the repository
  3. Create a branch named appropriately for the issue (based on the develop branch)
  4. Make happy code
  5. Submit a pull request to merge your changes to the develop branch
  6. Watch for comments or questions about your changes

Branch Naming

From now on, all work will be performed in feature or bug branches. The will follow this pattern: <issue_type>/<issue_number>-<short-description>.

For example, say I was working on issue #63, the branch would be called bug/63-fix-unit-tests

Something went wrong with that request. Please try again.