csharp

Using ASP.NET Core Dependency Injection to wire up a strategy pattern implementation to harness SOLID design.

Running the aspnetcore Github webhook locally.

Reducing the coupling of code dependent on DateTimeOffset

Looking at the secret values and how they work to allow for the AzureAlertWebHook webhook to process.

Running the ASP.NET Core Webhooks project locally and debugging the AzureAlertWebHook end point.

Looking at getting and building the ASP.NET Core Webhooks project on your development machine.

TL;DR - no, no, no! Ok, this was a bit blunt, so why shouldn’t you use nullable bools? Let’s start from the beginning … A boolean in .NET is a struct hence is a value type and can not be null. By definition a bool value is either true or false; binary the basic building blocks of computing. Code when written should be clear and through how it is constructed should show intent, I do not believe a Nullable<bool> (or bool?...

20180918 - Updated the link to HttpServiceCollectionExtensions.cs as the original link no longer worked. Thanks Gareth! After starting to write a service in aspnetcore I needed to access the current HttpContext to get access to the current logged in user. Injecting HttpContext use to be very bad in previous versions of asp.net so I investigated how best to get access to items on it in the new world. This is where I discovered the IHttpContextAccessor interface and a whole new world opened up for me....

With every new version of C# a new version of Resharper appears. It teaches me the new language features and how I can write my code in the new way. It’s not always right as the code it converts to can be unmaintainable so you have to be careful. But every now and then it makes me realise why I pay for a great productivity tool. public FeatureController(ApplicationDbContext applicationDbContext) { if (applicationDbContext == null) { throw new ArgumentNullException("applicationDbContext", "Argument cannot be null....

I was creating a couple of ViewComponents this evening in aspnet core and needed access to the ClaimsPrincipal of the current logged in user. Like the MVC Controller I was expecting the User property of the base class to be a ClaimsPrincipal however I was wrong and it was only a IPrincipal. Was this a bug? Had I missed something? Did I really need to cast User to being a ClaimsPrincipal?...