Do you like VS Code for code editing? Do you recognize that feeling that VS Code is just not for you because it is not convenient enough working with your C# project? You are just like me! I really like VS Code for editing tons of file types, but just not my C# projects because VS Code lacks that last bit of convenience working in a solution. The C# Dev Kit may change your take on this, it did change mine...

Azure DNS Private Resolver is a feature within Azure DNS that allows you to host and resolve domain names privately within your virtual network. By creating a private DNS zone and associating it with your virtual network, you can manage DNS records and use fully qualified domain names (FQDNs) to access resources within the network. The Azure DNS Private Resolver ensures secure and internal name resolution without relying on the public internet, providing privacy and security for your virtual network resources.

Going passwordless is a thing. Where we would use a connection string or a username and password in the past, we now like to eliminate these secrets and try to connect to (cloud) resources using identities. In the case of the Azure cloud, System Assigned or User Assigned identities. While for the majority of services, it is pretty straightforward to work passwordless, for some resources it may be a little bit more of a challenge.

This post takes it up a notch by automating the VM Image build process making use of Packer. Read this post to see the full deployment script and Azure DevOps pipeline to get build custom VM Images yourself in no-time.

Azure DevOps Scale Set Agents is a sophisticated Agent Pool that you can add to your Azure DevOps project in order to automatically scale pipeline agents depending on the demand in pipeline jobs. One of the downsides is that the image the Scale Set uses to spin up VM's, may not have the appropriate tools to run your pipeline. This forces you to install those tools when the pipeline is running. A time-consuming and unnecessary exercise. In this blog, I explain why, and how you can reduce the amount of time your pipelines run.

Configuration can be challenging in ASP.NET. There can be multiple sources and it may be a challenge to predict exactly what configuration values your system works with. Especially when this system runs in a (cloud)production environment that cannot be accessed easily. Adding validation to your configuration may help you get your system up and running in a healthy state, or at least provide you with some meaningful errors when your configuration contains errors.

This post is about deploying a web app (in this example an Azure Functions app) to Microsoft Azure with GitHub Actions. The resources are deployed using infrastructure as code. Once done, the GitHub action workflow will deploy the function app.

Lessons learned from visiting conferences both as an attendee and as a speaker. What is the impostor and how to deal with him(/her). This blog is more on the personal side and (hopefully) gives some insights into how I deal with the impostor syndrome most of us speakers have.

Setting a CORS policy for Azure Container Apps hosting a Function App seemed to be somewhat of a challenge. In this post, I explain what the problem is and how you can solve it. Yes, you CAN set a CORS policy on an Azure Container App hosting an Azure Function, you only need a couple of environment variables.

The base cloud infrastructure for PollStar is there and the first services are deployed. Now let's go and dive a little bit deeper. The blog is about scaling services. As you may have noticed in the previous post, the Sessions Service scales based on HTTP traffic. This post explains how to scale services based on events using KEDA. KEDA is an abbreviation of Kubernetes Event Driven Autoscaler.