Visual Studio 2019–Editorconfig UI

As I read more code than I write, code consistenty and readability are really important for me. That is why I like the .editorconfig and one of the reasons why I blogged about it before:

Introducing .editorconfig: https://bartwullems.blogspot.com/2017/04/visual-studio-2017editorconfig.html
Generate an .editorconfig: https://bartwullems.blogspot.com/2019/10/visual-studiogenerate-editorconfig-file.html
The ‘dotnet format’ command: https://bartwullems.blogspot.com/2020/04/dotnet-format.html
Let private fields start with an underscore: https://bartwullems.blogspot.com/2019/12/editorconfig-let-private-fields-start.html
Code cleanup in Visual Studio: https://bartwullems.blogspot.com/2019/10/visual-studio-2019code-cleanup.html

Although I really like EditorConfig files, configuring them is not that easy. If you agree then I have great news for you! Starting from Visual Studio 16.10 an EditorConfig designer was added that allows you to easily view and configure your code analysis preferences.

Check that you have at least version 16.10 of Visual Studio
Open the solution containing the editorconfig file
Click on the .editorconfig file. The designer is loaded:

The great thing is that if you are looking for a specific setting, you no longer have to open up the documentation but that you can easily search using the provided UI.

Remark: If you still want to edit the file directly in the text view, you still can by pressing F7.

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 ...

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.

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’: ...

The art of simplicity

Search This Blog