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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...