7.1.4 Installation Issues

It is assumed that the DTM vendor will provide a SETUP.EXE to install the needed components for his DTM. This will not be discussed further. Other than the actual components, the main issue affecting COM software is management of the Windows Registry and Component Categories. All FDT components must have a version information resource containing at least a version number, so that an installation tool can decide whether it can overwrite an installed component or not. Furthermore a Frame Application is responsible to install all FDT related XML schemas. A DTM has to use these documents provided by the Frame Application via IFdtContainer::GetXMLSchemaPath(). DTM specific schemas within FDT related XML documents must be declared as an inline definition.During the de-installation of FDT related components, the procedure has to take care about the availability of the FDT related interface description To avoid problems the usage of Microsoft Installer Technology is mandatory. This means all Merge Modules provided by FDT-JIG must be used. E.g. it is not allowed to copy the FDT100.dll directly on the PC. Furthermore all common DLLs (e.g. for usage of ATL, VB runtime or third party controls) must be installed via a Merge Modules if provided by the vendor of the DLL. Furthermore it is highly recommended not to include the FDT specific Interface description (IDL) within own components.

© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL.
This website is published for support of M&M products as granted in license conditions, chapter 2.1.
Last updated 2015-02-05 15:17
Email: FDT Technical Support Line.