Figure 7. New fields in the form of a working element in the example uses a static set of data for each list. If you plan to use dynamic data to the global list, for example, from external sources, you can write an external application that will receive information and update it with the utility import the global list of command line glimport. Using custom controls do not always use built-in UI elements satisfy the necessary conditions for their use. To extend the capabilities and more flexible data manipulation is recommended to use custom extensions to the interface. Here are some reasons that may encourage the use of custom elements for dynamic lists: Standard Constructors rules do not satisfy the necessary conditions, using very large amounts of data, data from an external source is used, value will be stored in another place, rather than in a standard data repository of work items, preparation of the project to create and edit custom extensions interface is IDE MS Visual Studio 2005 or 2008, and the use of the also allowed the expansion in both versions of MS Visual Studio. For the new user control to create the project as Windows Control Library (see Figure 8).

Figure 8. Creating a new project In addition, a class that is created must implement the interface IWorkItemControl. This interface is defined in the assembly Microsoft.TeamFoundation.WorkItemTracking.Controls.dll, which is usually located in the directory : Program FilesMicrosoft Visual Studio 8Common7IDEPrivateAssemblies. Also need access to the assembly Microsoft.TeamFoundation.WorkItemTracking.Client.dll, which is a description of the main classes, needed to work with a work item.