Published: Apr 3, 2019 by Adam Vincent

Welcome to my blog! It took me a while to find a low-overhead blog solution, but I believe this setup is what I’m finally going to go with.

The site is statically generated by Jekyll.
It is stored on Azure Blob Storage.
It is served through Azure Content Delivery Network.
The Jekyll build and deployment to blob storage is fully automated through Azure DevOps.

What this effectively does. I only need to write a simple markdown file to draft a blog entry. When I complete the blog entry, I only need to issue one fire and forget command: git push origin master. Once I issue the git push, it triggers the build process which generates the site with my new markdown post. As soon as that is finished, the release pipeline takes the site and plops it on Azure Storage. From there, the CDN does its thing and propagates my site globally. Having the site statically generated, coupled with the CDN that equates to very fast load times and global redundancy.

Smart Line Break

Quick-Start: Connect ASP.NET to Azure SQL with an Azure managed identity

Connect an ASP.NET Application running on Azure Web Apps to Azure SQL and leave no messy secrets laying about in the web.config file, depending on Azure Key Vault, or have to orchestrate building a connection string with via Azure Resource Manager.

Visual Studio Tricks: Increase signal to noise in your debugger

Inspecting your objects in Visual Studio’s debugger can sometimes be tedious having to expand objects, arrays and lists trying to find that ‘problem child’ of yours. Fortunately for us, there are some handy tricks to reducing the noise, and focusing in on the members of your object that are important.