It sounds like you're experiencing an exception from either an application issue or from not marshalling the thread back to the UI. Another source of exceptions is from various HTTP errors while communicating with Twitter. Since you're using
Windows Forms, you'll use a Control.Invoke to perform the marshalling:
You can probably find plenty of examples of how to use this on the Internet. The Silverlight Samples in the downloadable source code show how I used Dispatcher.Invoke with a lambda to keep the code inside of the callback, so there's multiple ways to
For the exception handling, just in case there's an application error, you can wrap the whole query in a try/catch. However, that isn't the only place an exception can occur and you might want to wrap the code inside of the callback lambda in a try/catch.
Essentially, you'll need to determine the cause of the problem to figure out what is happening and figure out a strategy. Be sure to drill down into the exception in case it's being wrapped by something like a TargetInvocationException or to find
more details if it's an HttpException. Fiddler, F12 tools, or Firebug can help with HTTP errors. One thing I would do is implement the marshalling of the callback onto the UI thread because that can definitely crash your application.