Development Articles

Humanizer is a great open source library for taking things that aren't human friendly and making them human friendly, and it has amazing support for different locales and such. However, the default installation package includes a LOT of languages, and many times individuals are overwhelmed with the clutter that happens with it. Lets explore some procedures that you can use to trim this down.

A few months ago I discussed some basic configuration elements for the then "freshly released" Copilot Coding Agents. A lot has happened in the last 4-6 months, and I thought it would be worthwhile to revisit things a bit and show how to get started with your projects.

I'm a huge fan of Entity Framework Migrations, using them for almost all client projects. In a given week, I will see dozens of changes deploy to production successfully across our portfolio of projects. However, there is always that "one task" that results in a failure and each time it happens it triggers an update to our internal training and review processes, and it has to do with repeatable scripting and the use of the "idempotent" flag. I thought I'd share our experiences with everyone, to help prevent issues for others.

With the recent preview release of GitHub CoPilot Agents, the importance of proper instructions for the agents is as important as it ever has been. But how do I effectively manage this when we have limits on the prompting depth and what items it has access to?

I'm an avid supporter of Open Source software; I maintain multiple projects, contribute to others, and sponsor developers across numerous projects I use or care about. However, there has been a recent trend in license changes with open source software that create a unique and real risk to companies and development teams that could go unnoticed and result in a catastrophic impact on organizations. Let's explore how we select, integrate, and manage the usage of third-party solutions.

There are many discussions regarding the cadence of upgrades and the burden of keeping up to date with the .NET releases, but that is all a topic for another day. Today, I want to take a moment and talk about the unsung heroes of constant updates: improved performance!

ASP.NET Identity is fantastic and provides a quick method for implementing user security in your applications, however, the process of inserting system defaults is not exactly the most straight forward and there are many ways to look at it, so lets explore some options.

The most common deployment process for Windows implementations of .NET MAUI Blazor applications is to utilize the automatic MSIX package creation. However, there are situations where you may need to deploy your application as a simple exe so you can deploy it to the location of your choice or as in my case so that I could pass parameters at launch to the application.

Windows 11 added the ability to set up a Dev Drive that is targeted for key developer workloads, and after soliciting some experience from others, I thought I would try it out myself. The results were impressive and immediate, and something I'm rolling out to our entire team.