We decided to use Qt for our next Geospatial Intelligence Desktop App, but the .NET Core performance was close to Qt and both easily outperformed the JavaFX prototype. So, we are going to use .NET Core for our Geospatial Intelligence Services backend. 

Drum is a little library for building URIs to ASP.NET Web API actions, using direct routes and lambda expressions. It provides an alternative to the UrlHelper class. Instead of requiring a route name and a set of name-value pairs, Drum allows the creation of URIs using actions invocations.

// using UrlHelper 
var uri1 = _urlHelper.Link("GetPaged", new { page = 0, count = 10 });

// using UriMaker
var uri2 = _uriMaker.UriFor(c => c.GetPaged(0, 10));

where GetPaged is a Web API controller action

[RoutePrefix("api/UriMakerTests/resources")]
public class ResourceController : ApiController
{
    [Route("", Name="GetPaged")]
    public HttpResponseMessage GetPaged(int page, int count) {...}

    ...
}

So when Microsoft acquired Xamarin in 2016 and started integrating the Xamarin Visual Studio plugins more with the standard VS features, I knew I had to try and switch over to take advantage of the powerful IDE and language. Some of the immediate benefits I gained from the switch are:

• Simple asynchronous programming
• Access to powerful plugins like ReSharper
• Freedom to work in Windows or OSX
• Access to powerful debugging tools for the Android on Windows (debugging iOS on Mac side is good but can be buggy).
• Access to built in NuGet package management for third party libraries 

At last, SQL Server has caught up with other RDBMSs by providing a useful measure of JSON-support. It is a useful start, even though it is nothing like as comprehensive as the existing XML support. For many applications, what is provided will be sufficient. Robert Sheldon describes what is there and what isn't. 

Professional REST API design with ASP.NET Core and WebAPI

This project is an example of lightweight and extensible infrastructure for building RESTful Web API with ASP.NET Core.

This example contains a number of tricks and techniques which I've learned while building APIs in ASP.NET Core.

Techniques and Features

•  JWT Authentication
• Secure JWT using Encryption (JWE)
• Logging to File, Console and Database using Elmah & NLog
• Logging to sentry.io (Log Management System)
• Exception Handling using Custom Middleware
• Automatic Validation
• Standard API Resulting
• Dependency Injection using Autofac
• Map resources using AutoMapper
• Async/Await Best Practices
• Versioning Management
• Using Swagger (Swashbuckle)
• Auto Document Generator for Swagger
• Integrate Swagger and Versioning
• Integrate Swagger and JWT/OAuth Authentication
• Best Practices for Performance and Security 

A guide to understanding the importance of commit messages and how to write them well.

It may help you to learn what a commit is, why it is important to write good messages, best practices and some tips to plan and (re)write a good commit history. 

What are some examples of websites that use .NET Core?