Mitch's Blog

In less than 60 minutes you can establish an end-to-end CI/CD process in Azure DevOps to truly automate the build and release of .NET Core applications. This post showcases our process for this.

With Microsoft Azure it is easy to create an application environment that is replicated across different geographic regions, however, the documentation makes it look more complicated.

It is possible to deploy DNN Platform in a manner that supports geo-redundant operations, however, there are multiple items that need to be evaluated and resolved to do so safely.

Azure App Services support many technologies, and are configured to be "quick start". This is great for getting going, but might expose you to more than an acceptable amount of risk in the long-term.

The decision to migrate to .NET Core, or to not do this, is very hard. This post explores some of the considerations that I take when I work with customers.

Code coverage analysis is great, but what is even better is to include this information in your Azure DevOps builds. You can quickly add this functionality to your project with a small change.

So, you have to upgrade to .NET Core 2.1, but it failed! Now, what do we do? Quick fixes to common errors.

.NET Core 2.1 was released today, and it is a mandatory update for many users due to the new support policy & lifetime.

Published documentation from Microsoft shows us how to use dependency injection inside of a single project, however, the real-world is different. This post explores some options for managing dependency injection.