Microsoft attorneys have signed off on the open source release of the DotNetOAuth source code that I’ve been building in my spare time. It should show up in the public git repo in the next 24 hours. What’s up there right now is several weeks old and tons of progress has been made that I’m eager to publish.
Once it’s published I’d very much like to get some feedback on the public API, and any holes in what it supports.
And now a review of what’s coming…
I’ll publish the DotNetOAuth source code first as a separate library just so you can get at it sooner, since that’s its current form. I’ll eventually merge it into the DotNetOpenId library for its final release. But I hope many of you will try it out in its separate library form and give lots of feedback, particularly on its public API including ease/difficulty of use and discovery, and scenarios that are not yet allowed or difficult given what I’ve exposed.
I have samples demonstrating both Service Provider and Consumer roles. The Consumer sample demonstrates downloading your Gmail address book using OAuth. Then both Consumer and SP samples work in tandem to show off WCF with OAuth authorization. For those of us working more in the .NET or SOAP worlds, WCF is a great API for making data queries from one web site to another, and adding OAuth is really exciting.
And of course unit tests (currently 140 of them) verifying correct behavior. The tests are written to use mstest.exe rather than NUnit. Whether it stays that way is still flexible, but since I’m writing all the code at this point and find mstest to be more convenient and easier to measure code coverage for better testing, that’s what I’ve chosen for now. With the right set of #ifdefs, I just might be able to get compiles to work against either unit test library, but it hasn’t been a priority yet.
As revealed before, this library takes dependencies on .NET 3.5.