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

Popular posts from this blog

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.

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...