Table Of Contents

Custom Device Non-Standard XML Element Types

Last Modified: June 10, 2021

Non-standard element types are defined in the Custom Device.xsd schema.

Dependency

The Dependency element type describes a dependency of the custom device, such as a DLL or VI, that the custom device requires and that you want to deploy to the target with the custom device.

Element Required? Element type Min/Max Occurrences Description
<Type> Yes xs:string 1/1 Specifies if the path you specify is relative or absolute. Valid values are Absolute, To Base, To Common Doc Dir, or To Application Data Dir.
<Path> Yes xs:string 1/1 Specifies the path to the dependency on the host computer.
<Behavior> No xs:string 0/1 Specifies whether the path is Static or Dynamic.

LocString

The LocString element type specifies English and localized strings to display in menu items.

Element Required? Element type Min/Max Occurrences Description
<eng> Yes xs:string 1/1 VeriStand does not currently use this string. The <loc> string appears in the shortcut menu.
<loc> Yes xs:string 1/1 Specifies a string for a custom shortcut menu. You can use two colons (::) to separate elements and create nested menu items.

Path

The Path element type describes a path to a file and whether the path is relative or absolute.

Element Required? Element type Min/Max Occurrences Description
<Type> Yes xs:string 1/1 Specifies whether the path you specify is relative or absolute. Valid values are Absolute, To Base, To Common Doc Dir, or To Application Data Dir.
<Path> Yes xs:string 1/1 Specifies the path to the file.

Target

The Target element type describes the target to which you want to deploy the custom device.

Element type Enumerations
xs:string
  • All
  • Pharlap
  • Windows
  • Linux_32_ARM
  • Linux_x64
  • PharlapWindows

VersionType

The VersionType element type specifies version information.

Attribute Required? Attribute type
Major Yes xs:unsignedInt
Minor Yes xs:unsignedInt
Fix Yes xs:unsignedInt
Build Yes xs:unsignedInt

Recently Viewed Topics