With this single line in change log:
Change – Removed .NET 4 portable class library target from NuGet package
Json.Net has also removed the Silverlight 5 support.
James Newton-King – Json.NET 10.0 Release 1 – Async, performance, documentation and more
A middleware to provide specific html pages for some error and default one for others while returning correct http error code as status: Re-execute the middleware pipeline with the StatusCodePages Middleware to create custom error pages.
We can also want to know the original path that actually caused the error: pretty easy using Request Features in ASP.NET Core and querying for IStatusCodeReExecuteFeature. In fact, current implementation of this interface also provides error query string (but it will not be reflected into interface before .Net 2.0): Retrieving the path that generated an error with the StatusCodePages Middleware
All is already said in title: Using strongly typed configuration in .NET Core console app.
Main interest of this post is to reaffirm that strongly typed configuration is not restricted to Asp.Net core. After all, an Asp.Net core are only command line programs making some http listening.
Around computing 