In addition to the AppMod.src file that is added to your application directory when you create a new script application, a specialized file named, "GDI.wif" is included.
GDI.wif files identify subdirectories within the VTS installation directory as containing the resources required to run a VTS application (either standard or script). The contents of the GDI.wif file for a script application are displayed below.
New Script Application
d4535c19-e4c9-420c-bd62-a5d09ac5c0bc
System
Every GDI.wif file (whether for a standard or script application) contains the following 5 lines:
1. The first line of the GDI.wif file identifies the title of the application (in this example, "New Script Application").
2. The second line identifies the parent application layer. Because this is a script application, it is not based on the VTS layer. Therefore, the second line in this example remains blank. (A standard application would display either "VTS\" (indicating the VTS layer) or the name of the OEM layer upon which it is based on this line.)
3. The third line identifies the GUID or globally unique identifier for this application. This is a unique alphanumeric string granted by VTS exclusively to this application, and is the means by which VTS recognizes this directory as an application directory.
4. The fourth line is the link to the compiled form of the application. In the case of a standard application, this would be the name of the application's directory. In the case of a script application, this is "System".
5. The fifth and final line identifies the name of the ODBC data source that enables access to the application's tag properties database. Again, because this application is a script application and as such is not based upon the VTS layer, there is no tag properties database, and therefore no ODBC data source required.