Skip to main content

Goodbye Visual Studio macro’s, we will miss you…or not

For the people who have missed the news:

In the next version of Visual Studio(Visual Studio 11) the macros automation feature is taken out. This includes macro record/replay, macro projects and the Macros IDE. Based on some usage data that showed that less than 1% of Visual Studio developers use this feature, they decided to not invest in this feature anymore and focus on other improvements instead.

So starting from VS 11, if you want to automate some behavior in Visual Studio, you’ll have to create a Visual Studio extension.

You have the following extension options at your disposal:

  • Visual Studio Package: This is used for the older VSPackage style pugin-ins.
  • Editor Classifier: Used for creating your own syntax highlighting
  • Editor Margin: Used to adorn the margins in an editor window
  • Editor Text Adornment: Used to adorn text within an editor window
  • Editor Viewport Adornment: Used to place editor visuals relative to the editor’s visual surface
  • [VB/C#] Item Template
  • [VB/C#] Project Template
  • VSIX Project: This is the newer plug-in model that is most commonly seen in the Visual Studio Gallery
  • Windows Forms Toolbox Control
  • WPF Toolbox Control

In addition to the language specific templates there is a generic extensibility folder containing:

  • Visual Studio Add-In: This is a wizard that lets you create add-ins using C#, VB, C++ ATL, or C++ CLR.
  • Visual Studio Package: This is another wizard that lets you choose between C#, VB, and C++.
  • Visual Studio Shell Isolated: This lets one create applications based on the Visual Studio IDE itself. An early example of this is the AddOn Studio for World of Warcraft.

More information:

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