Startup errors in your ASP.NET Core middle-ware can cause real headaches. The 500/502 errors often don’t provide enough useful information to debug, often leaving us stumped for hours as we try to troubleshoot the root cause problem. While upgrading another piece of our site, we hit it again, but this time around, we let ourselves be sidetracked somewhat, and vowed to get to the bottom of the best ways to troubleshoot and prevent these errors going forward.

In this post, you will find some useful tips and libraries that will help you get a head start on your SaaS application using ASP.NET Core and Azure.

The way storage is designed for Azure App Service is very interesting. Unlike with Heroku (or other similar providers), App Service offers a shared, persistent storage for your application. This generally means, that when one instance in a farm makes a write to the file system (D:\home) it will be available for all the other instances in the farm and it is going to persist even if the farm restarts or recycles.

One of the questions you may have is “Why do you say it is important when there is Azure Container Service?” The answer to that is very simple and very straightforward: Take the power of App Service on Windows with all of its services (scalability, custom domains, continuous integration, …) and leverage its power with your custom environment thanks to Docker.

The initial problem with App Service is its slow filesystem (which I have blogged about already more than once). Up until this discovery you had two options – either have all the files delivered through the slow replicated filesystem or enable Local Cache which results in the files written locally no longer being persistent which is a major issue with most PHP applications (even for full WordPress functionality – installing plugins, updates, etc.). Now, there is a third option ...

This article explains from scratch how to publish ASP.NET Core 3.0 Web App / API in Azure Linux App Service with using self-contained mode.

With Visual Studio 2019 we can publish ASP.NET Core 3.0 applications as self-contained executable. It’s especially useful for environments where ASP.NET Core 3.0 is not installed or where we don’t have permission to install it. Here’s how to do it.

.NET Core Worker Service, we created a .NET Core Worker Service and then showed how to host it as a Windows Service. This week we will be taking the application created in last week’s post and publishing it to Azure.

Azure EventGrid to power our event-driven application written in ASP.Net Core. In this blog, I wanted to take a moment to demonstrate how to locally debug an ASP.Net Core Web API that receives messages from Azure EventGrid.

MVC projects in ASP.NET Core have a built in feature to provide information on the health of your website. It’s really simple to add it to your site, and this instrumentation comes packaged as part of the default.