…ok more like a nuget package structure.
…reaming dlls in the main package.
… to perform a conversion.
…verflow issue reported by 'tonwinemaker'
… our converters correctly. We'll need to look into the JSON.net changes more before moving up to the latest versions. Fixed OAuth signature being generated incorrectly for streaming connections. Added Silverlight support back to Twitterizer for the entire library. Added/updated list endpoints and options Improved Stream event deserialisation Fixed ignore folders. Added MaxStatusId to Favorites Added Hack for bad tracking cookies being sent from twitter on Siverlight search and api calls. Fixed a few bugs with Trends deserialisation
…code from silverlight projects (not supported).
Removed all caching support. Dropped the OAuthUtility.GetAccessTokenDuringCallback helper method. Dropped the 'Twitterizer2Lite' project. Removed reading configuration setting for SSL (really slow). Silverlight and Sliverlight async libraries are no longer signed/strongly named because JSON.net isn't, so we can't. Added a README file for github.
This patch adds a UseCompression to the StreamOptions class. This in turn changes whetherr the request response stream is compressed using the GZip/Deflate compression methods.Please enter the commit message for your changes. Lines starting
Added git ignore file.
… My bad, sloppy proof reading of my changes.
…nsoft.Json.4.0.5. Changed TwitterStream to close immediately when invoking EndStream(), instead of lingering about. Removed unused method parameters to EndStream(). Invoke EndStream() from Dispose(), to make sure the stream is always closed properly.
…string.Trim() method (without arguments) to get rid of all whitespace (both unix and windows). -Added a check for .HasValues on all Json objects before deserializing them in ParseMessage. -Converted an Action.BeginInvoke to a ThreadPool.QueueUserWorkItem, as the first one doesn't report unhandled exceptions (due to it being used without a callback that did EndInvoke). Any exception thrown by the ThreadPool will at least be caught with the UnhandledException handler in client apps.