Designing the Toolkit Configuration File

The name of the toolkit configuration file informs UFT of the new supported environment. After you deploy this file to the correct location on a UFT computer, when UFT opens, it displays the environment in the Add-in Manager, as a child node beneath the WPF Add-in. If you select the check box for this environment, UFT loads the support that you provide for it. (If you are working with Silverlight, you must also select the Silverlight Add-in.)

The configuration file content defines how the controls are supported, which test object classes and custom servers are used for each custom control and so on.

Open the MyWpfToolkit.cfg file to see its content.

The MyWpfToolkit.cfg file was created automatically based on the specifications you provided. Therefore, it already has all of the necessary content to support the WPF Calendar control is the MyWpfToolkit environment.

<?xml version="1.0" encoding="UTF-8"?>
<Controls>
  <Control Type="Microsoft.Windows.Controls.Calendar" MappedTo="MyWpfCalendar“>
    <CustomServer>
        <Component>
            <DllName>CalendarSrv.dll</DllName>
            <TypeName>MyWpfToolkit.CalendarSrv</TypeName>
        </Component>
    </CustomServer>
  </Control>  
</Controls>

The Control element's attributes specify that the controls of TypeMicrosoft.Windows.Controls.Calendar (the full control type name including namespaces must be specified) is MappedTo the test object class MyWpfCalendar.

The CustomServer > Component element specifies the custom server DLL and type that provides support for this control type.

Note: The custom server type must be a full type name including namespaces, and in Silverlight it must include additional information, as described in the Toolkit Configuration Schema Help.

For more information on the elements and attributes in the toolkit configuration file, see the Toolkit Configuration Schema Help .

Continue to Designing the Test Object Configuration File.