Today our team ran into a strange issue when updating one of our Windows servers when all of a sudden our Prometheus monitoring stopped working. It turns out that this service, which should start automatically at startup, sometimes has issues starting up when Windows is performing an Windows Update forced restart.…
Both these configurations are "non-defaults" so they are very easy mistakes to make.…
Yesterday I was asked to take a look at one our clients Azure DevOps pipeline that stopped working all of a sudden. No changes had been made recently but from nowhere the VSTest pipeline task throws this error (followed by a bunch of other build errors).…
As I might have mentioned, I’m using a Macbook and I recently switched from using VMWare for my Windows development (.NET Framework) to Azure Virtual Desktop and I have not regretted this decision for a second. However when setting up my Azure Virtual Desktop I had som issues installing Docker and I thought I would share the solution.…
Yesterday I was helping our frontend team to set up a new CI workflow moving from Teamcity + Octopus Deploy to Azure DevOps pipelines and I ran into a weird issue that I thought I would share the solution to in case someone runs in to the same issue.…