New blog post: A quick guide to integrating the new Azure Service Bus Emulator with .NET Aspire, including an Azure Functions queue trigger and custom commands in the Aspire dashboard.

https://www.wagemakers.net/posts/aspire-functions-service-bus

#aspire #dotnet #azurefunctions #servicebus

@stooovie @mattrobertson so far I've found it interesting for long term trend analyses, like tracking the effects of insulation on energy usage.

@Jaffa @w8emv state machines is the way. I've found that other methods result in a big ball of mud and madness

@CEbbinghaus you could configure the rule CS8524 and disable the warning. The compiler will generate a default case for you so you will get runtime exceptions when someone casts an int to a non existing enum value.

Last year I've written a bit about it in more detail: https://www.wagemakers.net/posts/exhaustive-switch-expressions

Some thoughts on Swashbuckle.AspNetCore

https://www.wagemakers.net/posts/future-of-swashbuckle

#dotnet #aspnet #openapi #visualstudio

@oskardudycz I worked on a Gatsby site in the past, didn't really have a good time. We're moving to Astro now. Also running my blog on Astro for the past year or so, really like it.

Blogged: Integration testing Azure Functions triggered by Azure Service Bus messages

https://www.wagemakers.net/posts/testing-service-bus-trigger-azure-functions

#dotnet #csharp #azure #testing #integrationtesting

@dreamykeaver@chitter.xyz mono is not very relevant anymore. Dotnet (core) has taken its place.
There is quite a lot of Dotnet development going on for Linux, but a lot of it is invisible backends of APIS and services.

Then I threw the lines into Photoshop, applied the bucket tool, and ... good enough!

@anthrocypher I've got this in an upcoming publication:

"Every line of code written today represents a testing, complexity, maintenance and refactoring burden your team will bear tomorrow, and the reality is that none of our customers want code. Our customers want _utility and functionality;_ code is a liability we accept so we can deliver that functionality. GenAI or not, nobody wants or needs an arbitrary quantity of code for its own sake."

Blogged: Building a night light and sleep trainer controlled by Home Assistant

https://www.wagemakers.net/posts/esphome-sleep-trainer

#homeassistant #esphome #homeautomation

Blogged: Fixing GitHub Copilot in environments with custom root certificates.

https://www.wagemakers.net/posts/github-copilot-custom-certificates

#vscode #visualstudio #github #copilot

This thread, but for every software component you introduce, is why you should think carefully before adding moving parts to your system.

Total cost of ownership is not the same as "how much code".

@noleli @mattwilcox same https://fontsource.org/

@devops_discussions the logic app and devops rest api is total overkill unless you create a giant amount of new repos every week

@OwenTyme @nixCraft C# is open source and it is has become a pretty nice language

Blogged: How to build a gas consumption dashboard in Home Assistant with Grafana

https://www.wagemakers.net/posts/homeassistant-gas-usage-in-grafana

#homeassistant #homeautomation #sustainability #grafana

@Nick_Craver or both

@billseipel Absolutely, it really depends on your organization, size and rest of the Azure configuration. Some of the large organizations I work with have smaller subscriptions, scoped to only one team, for cost management. In that case traceability less of an issue.

@billseipel it's quite a common practice to share service connections. The alternative would be quite messy if you have many pipelines / apps