Azure Mobile Apps .NET SDK Releases
Adrian Hall (MSFT)
Today, we are releasing two new .NET SDK releases - v2.0.0 on the server side and v3.1.0 on the client side. The NuGet packages are available from the main NuGet repository and the symbols have been updated on symbolsource.
Azure Mobile Apps ASP.NET Server SDK v2.0.0
It's been a while since we updated the ASP.NET Server SDK. We've updated the base framework that we use to .NET Framework 4.6 and updated all the dependencies so that we are using the latest versions that we can while maintaining compatibility as a protocol level. In addition, we have deprecated the Azure Notification Hubs push registration endpoint. This is still included in the package, but marked as Obsolete and will be removed in a future version. You should use the App Service Push endpoint instead. In your ASP.NET Owin Startup class, you can remove the reference to .AddPushNotifications() from the configuration. App Service Push has been significantly enhanced over the last couple of months. It now supports white-listing of tags and automatic addition of tags based on authenticated claims available from the authentication provider. This lays the groundwork for re-introducing tag support into the client SDKs in a future release. In the interim, you can build your own Notification Hub Installation class and submit that via the .InvokeApiAsync() method. For examples on this, check out Chapter 5 of my Azure Mobile Apps book. We are also releasing the Swagger and Custom Authentication packages as generally available. You can read about the Swagger customization on our Wiki. Finally, we've also been working behind the scenes on updating the Azure Storage SDK, updating our testing and build processes so that those are more aptly done in the public, publishing more topics to our Wiki and adding information to our documentation.Azure Mobile Apps Client SDK v3.1.0
The Client SDK has had the following updates since the last update:- (#266) A bug that caused problems when two libraries both used SQLite. This was fixed by updating the dependency on the SQLitePCL.raw to the latest version. Thanks to Eric Sink for the fast turnaround on the fix for this, and for providing an awesome open source project that we can leverage here.
- (#215) We were inconsistent in the generation of GUID style primary keys between the client and server. We've standardized the production of keys to a hyphen-less version.
- (#196) We had a method for querying the underlying SQLite store that was not exposed. Sometimes, it's good to do queries against the raw tables stored in SQLite. We now expose the SQLiteStore.ExecuteQueryAsync() method that does the appropriate locking to ensure the operation is safe.
