You can implement custom control support without programming a .NET DLL by entering the appropriate Test Record and Test Run instructions for that custom control in a control definition file. (Create a separate control definition file for each control you want to customize.) You can instruct UFT One to load the custom control implementation instructions by specifying each control definition file in the .NET Add-in Extensibility configuration file, SwfConfig.xml.
Note: When extending support using an XML file, UFT One generates an ad hoc .NET DLL for you based on the XML file. This ad hoc .NET DLL becomes the custom server for the control.
When using this technique, you do not have the support of the .NET development environment—the object browser and the debugger— or the ability to create table checkpoints or output values. However, by enabling the implementation of custom control support without the .NET development environment, this technique enables relatively rapid implementation, even in the field.
This feature is most practical either with relatively simple, well documented controls, or with controls that map well to an existing object but for which you need to replace the Test Record definitions, or replace or add a small number of test object Test Run methods.
For more information, see Understanding Control Definition Files.