-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

CTW wrote:
> Hi,
>
> Tried posting this earlier but I'm not seeing it so apologies if
> this is a repost.
>
> I noticed there was only one .NET example in the Twitter wiki using
>  oAuth, and it doesn't illustrate how to handle PINs in a desktop
> app. So here are a couple examples based on the C# oAuth/Twitter
> library by Eran Sandler and Shannon Whitely, with modifications to
> handle the PIN stuff.
>
> http://www.codingthewheel.com/archives/codingthetweet
> http://www.codingthewheel.com/archives/coding-the-tweet-redux
>
> Are there any other popular C# libraries/wrappers for oAuth?
>
> Thanks~
I wrote one that does support OAuth with the PIN-based workflow--you
can find the code at http://twarp.googlecode.com. There's a binary
release and there's the source code in SVN trunk, which is a bit more
up to date (both support PIN-based workflows though). Samples are also
provided with the source distribution (and will be with the binary
distribution when I get around to repackaging it again).

Regards,

- --
Bojan Rajkovic <boj...@brandeis.edu>
Biochemistry '10, Brandeis University
PGP Signature Key ID: 0x8783D016
PGP Encryption Key ID: 0x2497B8B2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBCgAGBQJKY1JMAAoJEO4IwQyHg9AW4QQQANT3GgkJyk8NRWo3FIX1fA9o
iKZWbtkBHUM0XS1mAN3EbCfrltgSwipcDMKOzmjv0d2LhWsk+uy92e5GfnENcBle
bLSwZy3fplyTaP5ReUeN3WiBppaBYZJHqdHfcjoh+8z5NJ8T2qo2QbjBzcLO1iI/
gQlUo651YnkeR0il0PSYTpl+AOJdaVhPDil1mhw/XSAmTHGai4ZixxHvuNUYFdon
iweCDB5RAcZvkni0F5xIgAbdXvVm/TLPRPBDTva6fVJAN4Nt6MUDOP6RhLHvexFA
HRWGpr30eJ80HSBRvR2BGK6GboX5DvtcCV2BaCwMyzky8rV2uDYkXiezayDhdr0m
NUtsT2tzLbq22pf7/ZIo32B/FRxeYjCKfNkjZAAelPwRRSrJTkTwbz1AkSO2axNr
QMLt+fqROQyUATHaNXN16ZAgP7QzAycTaUWaIeI6svADUKv9Vl9y/OVNPGCbJ3Ef
biYLHsi8E215ePpgKHCunA+osjAJOqDUatwb597bf43A9j86I/xFZc7goXQfy7jX
l2zd7aPswuxmszealOkheiG68l9f3JvjF4IixOGUFHsOnNjPAouP2UA33VSfxxcm
D/A6tSd9dmGzYDK5TsvWEEJSYC8fCtLxwp/g5qYlYR6QPWEBPphSrbqwfAgdhQga
EN4DpXUrtEZCB7tElG8w
=wbUO
-----END PGP SIGNATURE-----

Reply via email to