Errors happen. That's a fact. When they do, we have tried to give you, the developer, the information you need to determine what the issue is.

When a request to Twitter fails, the library should, under normal circumstances, throw a TwitterizerException object. Catching this object should give you all of the information you need to debug.

Try this:

try
{
    // your code here
}
catch (TwitterizerException ex)
{
    // Look at the ex.Message, ex.RawXML, and ex.RequestData.ResponseException properties
}

When reporting an issue, please include the error message, Raw XML and stack trace of the exception thrown. Failure to do so will probably result in us closing and ignoring your issue.

Another useful way of finding additional information is to enable the request history feature. To do this, add an Application Setting (see below) to your application configuration file with the key "Twitterizer.EnableRequestHistory" and the value "true". Once enabled, include "TwitterRequestHistory.History" in the watch pane in Visual Studio. At any point, this will give you a complete history off all of the requests made to Twitter through the library. Each request will contain the url used for the request, raw xml returned by twitter, and the Users or Statuses parsed from that xml. It also contains the username and password used to authenticate the user, so the history should not be enabled in production environments.

Example configuration settings:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="Twitterizer.EnableRequestHistory" value="true"/>
    
  </appSettings>
</configuration>