netcore

This article describes how to configure your .NET Core application to serialize objects in camelCase instead of PascalCase.

This article explains another simple fix to an annoying issue. I guess that's how I start most of my little tutorials, but hey, it's true!

Recently, while building an app service to host a .NET Core API, I had to implement the logic for using both Read-Only and Read-Write Database Contexts for Entity Framework Core.

Sometimes you'll need the default identity for your ASP.NET Core application, but want to disable the registration of new users. Sounds pretty basic, right?

Every now and then comes the need to write your console output to a log file. There's a simple way to do this in .

This is another, kind of a classic and simple solution to a fairly simple problem: How to fix it, when your DbContextOptionsBuilder fails to take in your connection string and complains about UseSqlServer missing or whatever?

Another case, where there's plenty of documentation, but it just doesn't seem to be comprehensive enough or just doesn't apply for any of the cases that I have - for whatever reason.

When you're in your .NET Core project, it's always easy: you just register your DbContext in ConfigureServices, and then inject it into whichever Page, View or Controller you might need it in.

Just a quick piece of documentation, as this piece of code, has changed in different versions of .NET Core 3.0 so far a few times. Need to have things like this written down somewhere! UriHelper / NavigationManager with .NET Core 3.

Blazor is a new (ish) framework for building web UIs with C#.

Welp - just ran into this one, and as I expect others to encounter the same issue, I'd better document it right away! So in Blazor, I was crafting a simple component that'd display some data in a nice way.

Whilst building a proof-of-concept on .NET Core 3.0 preview 7 I ran into issues when developing web APIs.