As mentioned in my previous post I am currently switching my wife's eshop from Azure App Services to Azure Container Apps. The solution itself uses an Azure Functions project to perform asynchronous operations triggered via queued messages and uses Azure Application Insights for logging and monitoring.
I'm currently in the process to shift my blog from a WordPress website to a blog generate using a static generated website built with Next.js and hosted on Cloudflare Pages. During the initial setup of my Next.js site on Cloudflare Pages, I encountered an error message
I recently came across this tutorial on the new standalone javascript projects in Visual Studio 2022 via this blog post courtesy of Scott Hanselman. I was excited with the prospect of having standalone javascript projects inside of Visual Studio. Unfortunately I couldn’t move past the first step of creating the project as I was getting
The Problem My wife has been having an issue with her One Plus phone where the details of some contacts were not appearing in the Messages app. Even weirder, sometimes the contact details would show and other times they would disappear. I tried different things to try to sort this issue out such as: Clearing
I recently started working on a new project with .NET Core 3.1 using Azure DevOps as my CI/CD pipeline. I was using an on premise build agent (not hosted) with Visual Studio 2019 and teh .Net Core 3.1 SDK installed on it. I started getting the following error in the Nuget Restore step when attempting
I’ve been exploring Docker containers and using Traefik as a reverse proxy. I was trying to get the Docker example from https://docs.traefik.io/user-guides/docker-compose/basic-example/ to work with Windows Containers. When I tried to start the containers with the example, Docker returned the following error: ERROR: for traefik Cannot create container for service traefik: invalid volume specification: ‘/var/run/docker.sock:/var/run/docker.sock:ro’
I’ve been working on a project using .Net Core 2.2. During the course of development I needed to add an SQL Database project to the solution. Everything was building correctly on my local machin, however, the build started failing when I committed and pushed to Azure Devops. The initial issue was that the SQL Database
I’ve been working on setting up a service fabric cluster (read more on service fabric if you’re interested in the technology) using some old laptops I had lying around. I installed Windows Server 2016 without issues. Then I tried to install the WiFi drivers in order to have network and internet access on the laptops
I had some code running in production which uses fire and forget service broker conversations. I recently started having issues with queries reporting that the TempDb is full. This blog post explores this issue and how the issue was resolved.
I wanted to contribute to Ocelot, however when I tried to build the solution I got this error: “The current .NET SDK does not support targeting .NET Standard 2.0. Either target .NET Standard 1.6 or lower, or use a version of the .NET SDK that supports .NET Standard 2.0.” This blog post details the steps
Recently I’ve been testing out Docker for Windows. You can find more information on my experience here and here. Today, I started getting strange errors when I tried to start a container in docker. The error I was getting was: Error response from daemon: driver failed programming external connectivity on endpoint cranky_panini: Error starting userland