My OwaspHeaders.Core middleware hit version 18.104.22.168 recently. The new version uses a new way to set it's configuration: the builder pattern. So I thought I'd write a little about how the builder pattern works and how it is used by ASP NET Core and my middleware.
I decided to take one of my open source projects (OwaspHeaders.Core - https://github.com/GaProgMan/OwaspHeaders.Core) and update the code a little. It had previously used a json for configuration, but after this stream it used the Builder Pattern
I've taken a look at the most commonly asked questions on Stack Overflow for both .NET Core and ASP.NET Core and thought I'd write up what would be my answers here. Which questions did I ask? You'll have to click through to find out.
My third twitch.tv live stream was titled “SPAs a-plenty”. The goal of my this stream was to talk through Feature Folders and add them to a pre-existing GitHub repo, then to consume them in a new project for that GitHub repo. Things didn't go entirely according to plan, but it still ended up pretty interesting (I think)
I recently upgraded dwCheckApi to .NET Core 2.0, but the deployment didn't go so well. Want to know why and how to avoid it happening to you? Then click through and read on.
The Discworld Disorganiser is a Web UI front end for my dwCheckApi project, and was created as a way for users to search through the main Discworld novels. Users can search by Book data (title, blurb contents, isbn, etc.), Character name, or Series data (Character name, Book name).