Skip to main content

.NET Aspire Developers Day is coming up!

If you are part of the .NET community, you certainly have heard about .NET Aspire. It is a new framework/tool/set of patterns from Microsoft that allows you to build observable, cloud ready distributed applications. It’s main goal is to make it easier to build cloud-native applications on top of .NET.

Now if you didn’t had the time yet to take a look at .NET Aspire and want to learn what all the fuzz is about, I have some good news for you. On July 23, Microsoft will host the .NET Aspire Developers Day. This livestream event will be a full day of sessions with one common goal:

To show you how easy it is to harness the power of .NET Aspire, why it’s essential for modern development, and how you can leverage a vibrant community for support and innovation.

If you like to join, subscribe here for the event. Hope to see you all(virtually) there!

In preparation of the event, you can watch the recording of the Let’s Learn .NET Aspire beginner series:

More information

.NET Aspire overview - .NET Aspire | Microsoft Learn

Join Us for .NET Aspire Developers Day – Elevate Your Cloud Native Skills! - .NET Blog (microsoft.com)

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more