While hosting your ASP.NET Core Web App / API in Azure App services Windows/Linux, you would need to maintain configuration settings and secrets out of your application source code. This article explains how to manage settings in Azure.

In this article, we are going to learn how to Use Redis cache with ASP.NET Core using the package “Microsoft.Extensions.Caching.Redis” provided by Microsoft. The Cache is used to cache data which is frequently used and which does not change often.

In this article, we are going to learn how to Access Azure Redis cache using StackExchange.Redis.Extensions.Core Extensions. “StackExchange.Redis.Extensions.Core”

In this article, we are going to learn how to Uploading Download and Delete files in Azure Blob Storage using ASP.NET Core in simple steps.

Hosting cross platform ASP.NET Core Applications with containers in this two part series.

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 ...