Since I moving my blog into Azure (as detailed in a previous post), I had started to see a series of odd alerts being fired out, with lots of random 500 errors at odd times of the day & night. When I checked the website was fine. At first thought this was related to the Azure App Service I was hosting my site in, but it occurred to me that it could have been happening before, but I just didn’t know - Azure & the App Service was alerting me to stuff I previously had no visibility into
Recently I decided to move my Wordpress blog from where it is hosted in a virtual shared Linux environment (TSO Host) into Azure. The current hosting is fine and has served me well over the years, but seeing as my current job is working with Azure I wanted to experiment. In particular my role is focused on the PaaS web & app hosting services in Azure, so I wanted to see first hand what the experience was like, particularly for a non enterprise user.
Note. Since this post was written I’ve migrated my blog (twice in fact!). Once into a static site using Hexo and again using Jekyll. The blog currently is hosted in GitHub pages, and Azure and Wordpress etc is no longer a concern
The migration has been successful (hopefully this page loaded without errors!), so I’ve decided to capture my thoughts on the process and some of the challenges I encountered along the way
Final part of a series covering some of the fundamentals of ASP.NET Core, Docker and Azure. This part is fairly dependent on what we covered in part 1 and part 2. However if you want to skip ahead you can use my pre-created ASP.NET Core demo app on Github; https://github.com/benc-uk/dotnet-demoapp which you can clone and use to skip what was covered in part 1. However we’re going to need a running machine with Docker engine on so skipping part 2 isn’t really an option
Part 2 of a basic series covering ASP.NET, Docker and Azure. This part is independent of what we did with ASP.NET in part 1, and serves as a guide on getting Docker running in Azure. I’m not going to cover the basics of Docker or an introduction into why containerization is a Good Thing™ there’s a million other posts & articles out there on those topics
This is a very simple tutorial and 101 guide on getting an ASP.NET Core web application up and running. We’re starting from first principles, and we won’t get very deep into the vast world of ASP.NET, so you won’t find any details on topics like MVC, Routing or Entity Frameworks here. Our goal is to get a very simple web app & server running on your Windows/Linux/OSX machine
Note. This is a re-write of a older post, as the .NET SDK and tooling have changed significantly upon final release in March 2017, making the old post more or less obsolete
This is a series of posts providing a step by step guide on creating a ASP.NET Core web app, then creating a Docker host in Azure to run it, finally publishing and running your ASP.NET app as a Docker image & container. I’ve split this into three sub-posts to keep it manageable & readable.
You do not need Windows or Visual Studio for this exercise (welcome to the new Microsoft!), all tools used are open source and multi-platform, I’ll be using Windows for basic convenience. Naturally the Docker host will be on Linux.
The three parts are pretty much independent. If you already know ASP.NET Core or have an existing app you can skip part 1. If you already have a Docker host running somewhere (maybe not in Azure, heaven forbid!) then skip ahead to part 3.
You will need an Azure subscription for part 2, you can get a free subscription with $25 per month of credit via ‘Visual Studio Dev Essentials’