via Open Sesame: Parse .NET SDK.
.NET SDK is also now completely open-source!
Following the concept from our previous blog post, .NET SDK adopts the pattern of separating a component into
State is simply a dumb object that stores data, with C# we can construct
State directly with Object Initializer.
via Using Jil for custom JSON Serialization in the Couchbase .NET SDK.
One of the new features introduced in 2.1.0 of the Couchbase .NET SDK was support for overriding the default serializer with your own custom serializer by extending the ITypeSerializer interface and providing your own or favorite serializer. In this article we will show you how to do this and provide an example (clonable fromcouchbase-net-contrib project in Couchbaselabs) using a very fast JSON serializer called Jil.
By default the .NET SDK uses the popular NewtonSoft.NET JSON serializer mainly because it’s a feature complete, widely used and well-supported project. In general the performance provided by the NewtonSoft is good enough for most projects, in some cases however, you may want to use a faster JSON serializer like Jil.
This is bug fix and maintenance release for the 1.3.X version of the Couchbase .NET Client. It contains a number of bug fixes and a performance enhancement specific to add/remove node and rebalance scenarios. It is suggested that users of earlier versions of the Couchbase .NET 1.3.X client upgrade to this version. Read more>>
Lync 2013 ships with a Web API called UCWA, the problem is it’s almost as complex to use as the more advanced .Net SDK, and is a significant barrier to developers unfamiliar with Lync. Furthermore it isn’t designed with control in mind, so once you connect you’re free to do whatever you like with no restriction on message rates or monitoring.
One of the values that Azure Mobile Services provides is an easy way to implement authentication for mobile applications, via a very simple API – call a login function (or equivalent) on the client object in any of the supported platforms, and your user gets presented with a simple web-based interface that allows them to log in to your mobile service. This is what we call a server-side authentication flow, where the service guides the client to the provider (via redirections in the web page) and then back to itself.
Using a server-side authentication is a good way to start an application, but if the authentication provider which you want to use has some native SDK that supports login, then your user would have a better experience if your app used it. For example, if your user is in an android device, it’s very likely that they have a Google account associated with their device, so if they can use that account without having to re-enter their credentials, that makes for a better user experience. Same thing with a Facebook account in an Android, iOS or Windows Phone device, or a Microsoft account on a Windows or Windows Phone. This scenario is what we call a client-side authentication flow, where the client application talks directly to the provider (via its native SDK) and then just exchanges some token from the provider with the mobile service to authenticate with the service itself.
We’ve had the client-side authentication flow working for Facebook and Microsoft authentication in the node.js backend for some time, but not in the .NET runtime. We also didn’t support Google SDK authentication in any of the runtimes – until now. We just released support for Google authentication in the node.js backend, in addition to supporting authentication via data from SDK from all those three social providers in the .NET SDK. This has been a long-requested feature that we’re glad to see live. In this post I’ll walk through how to use this new feature.