.NET Articles

Background services are amazing, and the systems that provide built-in resiliency are even better! However, it is incredibly important that your solutions are architected in a manner that actually ensures that the resiliency doesn't create a risk of duplication or other issues.

With proper planning and consideration, .NET 11 RC 1 introduces the ability to go live in production with Microsoft support for production workloads. Is it a risk you should take? Is it valuable to do so this early, with the production release 2 months away? Let's discuss!

.NET 8 and .NET 9 reach end of support on November 10th, 2026. If you haven't made the move to .NET 10 yet, this post has a number of tips & checklist items to help you get your upgrade planned, tested, and deployed to .NET 10 before the deadline.

A production system ran reliably for years until bot traffic exposed hidden technical debt, exhausted its SNAT ports, and brought API calls down. Let's dive into what happened and explore how it might happen to you, and ways to combat and avoid these types of issues in the future!

Artificial Intelligence tools are quickly becoming an essential part of modern software development, and GitHub Copilot continues to lead the way in helping developers write code faster, solve problems more efficiently, and accelerate delivery timelines.

We have been in the honeymoon period with GitHub Copilot over the last 12 months, amazing functionality, huge improvements in productivity, and the ability to do things that are just amazing. That all came with some really, really low pricing, but that is all about to change, and the method of that change is still very much up in the air, but it is something that we need to plan for, and be ready!

With technology evolving at the speed of light, it is hard to manage upgrades and updates. Sometimes it is easy to get lulled into the "It builds" so its good enough mindset. However, there are a few quick steps that you can take to help reduce the burden of doing things the "right" way.

We love to think that users are proper in how they interact with our applications, or that they are able to do things in a way that is consistent with expectations. But, we all know that isn't actually the way life works! The 404 response is not only important for users, but it is also valuable for bots/search engines to disclose content that has been removed or otherwise. Lets dive in to how to do this properly with .NET 10 and Interactive Server Blazor,

Recently, when setting up CI/CD for a .NET MAUI project, I had a heck of a time getting what should have been a simple command to build, nothing like a bit of debugging issues to waste an afternooon. So I thought I'd spare everyone the hassle and share my experience hoping it helps you out!