AppNet.NET is a library which implements all endpoints and object from the App.Net API as documented at http://developers.app.net/.
There is a nuget Package available at https://www.nuget.org/packages/AppNet.NET
Find classes within the Model folder for every object type as documented by App.Net.
They are all in the AppNetDotNet.Model namespace (e. g. a post is of type AppNetDotNet.Model.Post
All API calls as documented by App.Net are implemented as static functions in the AppNetDotNet.ApiCalls namespace.
For example to get the My Stream contents you call
AppNetDotNet.ApiCalls.getUserStream("AAAAccesstokenxxxxxxx")
All return values are implemented as as Tuple of the content plus an object of type ApiCallResponse. This ApiCallResponse gives you infos about the sucess of the last call as well as the replied rate_limits and if an error occurs the reasons. It should never be null in any response - otherwise it would be a bug.
Example on how to get the My Stream of the current user:
Tuple<List<Post>, ApiCallResponse> result;
ParametersMyStream parameters = new ParametersMyStream();
parameters.count = 100;
parameters.include_annotations = true;
result = AppNetDotNet.ApiCalls.SimpleStreams.getUserStream`("AccessTokenValue", parameters);
if (result.Item2.success) {
List<Post> posts = result.Item1
}
OAuth is implemented within the AppNetDotNet.Model.AppNetAccount class. This includes the full workflow including the used browser window asking the user for permission for the desktop flow.
The server side flow is not completed by now (I don't use .NET on webservers myself - so if you want to contribute...)
Authorization is done by using a WebBrowser control. The downside is that this control by default only renders HTML in quirks mode which will bring a 404 error on authorization success (as the WebBrowser control is limited) and because of this you won't get the needed access token.
To enable the full browser mode you need to enter a parameter in the registry as described on this side. Remember to enter both Spinnaker.exe and Spinnaker.vshost.exe in your registry to have the debug version work also. Also remember that if you deliever a setup this setup needs to add those registry keys for the user automatically.
There is a second project included with a (very simple) test window to test all API calls and to have examples of their usage. See MainWindow.xaml.cs and the other windows for all used API calls
Sometimes the result is rendered in the test window (e. g. the found places and the places search) but most of the time set a breakpoint to see what happens.
Feel free to contact me @lighun any time if you questions or suggestions https://alpha.app.net/lighun