Skip to main content

TFS Build: using the built-in editors

By default when editing parameters inside a Team Foundation Build process template you get a very simple editor.(Except for some out-of-the-box available parameters).  But wouldn’t it be nice if you could give your users a much better experience by providing a custom editor?

TFS allows you to this by changing the Editor Parameter in the Metadata argument.

image

You could build  your own editor or you could start by using one of the built-in ones(available in the Microsoft.TeamFoundation.Build.Controls assembly). So just enter Microsoft.TeamFoundation.Build.Controls.{ControlName}, Microsoft.TeamFoundation.Build.Controls in the Editor parameter and everything is set.

image

A list of the available designers
Editor Description Screenshot
BuildAgentSelectionEditor Select a build agent. BuildAgentSelectorEditor
BuildProjectListEditor Select a project (typically a .sln or .csproj) from source control. BuildProjectListEditor
ServerFileBrowserEditor Select a file in source control ServerFileBrowserEditor
TestSpecEditor Select a spec of tests to run TestSpecEditor
WorkItemTypeSelectionEditor Select a work item type WorkItemTypeSelectionEditor
ServerFolderBrowserEditor Select a folder in source control ServerFolderBrowserEditor
StringListEditor Edition of a list of string. StringListEditor
EnumPropertyEditor Shows the list of possible enum values EnumPropertyEditor
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