by bill-s, 2019-02-25T08:25:56.791Z
In this pic there is a consumer of the API that can be any kind of application. The consumer sends a query to the API. Part one what GraphQL specifies is the format and syntax of the query. Part two is a runtime on the API that is able to process the query. When the runtime has processed the query it typically returns JSON, but that is not set in stone by the specification.
by bill-s, 2019-02-27T05:46:05.592Z
This post continues my series about writing high-performance C# code. In this post, we’ll continue from the last two posts by introducing the Span<T> type and refactor some existing code by converting it to a Span-based version. We’ll use Benchmark.NET to compare the methods and validate whether our changes have improved the code.
by bill-s, 2019-02-27T05:45:24.173Z
After making ASP.NET Core code coverage reports work on local box I made step further and made code coverage reports available also on Azure DevOps. This blog post shows how to generate code coverage reports for .NET and ASP.NET Core applications on Azure DevOps.
by ThomasArdal, 2019-02-26T07:43:23.343Z
My guide to using user secrets in ASP.NET Core.
by bill-s, 2019-02-27T05:44:51.375Z
The async and await keywords have done a great job of simplifying writing asynchronous code in C#, but unfortunately they can't magically protect you from getting things wrong. In this article, I want to highlight a bunch of the most common async coding mistakes or antipatterns that I've come across in code reviews.
by bill-s, 2019-02-25T08:26:23.735Z
My first draft of hierarchy traversing component got some serious feedback and it’s time to make some changes before moving on to next challenges. Hierarchy traverser is not optimal yet as it uses tail-call recursion and it’s easy to run to stack overflow with it. This blog post solves this problem and prepares for next challenges like node cache and continue-from-given-node.
by bill-s, 2019-02-25T08:25:26.787Z
Do you want to try the preview of Visual Studio 2019 but worry that your favorite extensions aren’t supported yet? A record number of extensions have already added support for Visual Studio 2019. So there is a good chance your favorite extensions are among them. In fact, more than 850 extensions are currently available, and more are being updated every day.