M&M FDT 1.2.1 Online Specification
 7.1.7 DTM Registration


Interfaces and Methods   -   Schemas   -   FDT Specification   -   Quicklinks   -   Abbreviations

Up to FDT Specification

7.1 FDT Registry and Device Information
7.1.1 Visibility of business objects of a DTM
7.1.2 Component Categories
7.1.3 Registry Entries
7.1.4 Installation Issues
7.1.5 Microsoft’s Standard Component Categories Manager
7.1.6 Building a Frame Application-Database of Supported Devices
7.1.7 DTM Registration

7.1.7 DTM Registration

DTMs have to write registry entries whenever the DTM is
  • Installed
  • Uninstalled
  • Modified, (e.g. new device types are supported or the DTM was updated (bug fix))
If the path doesn't exist, the first installed DTM has to create the path.

A FDT root path is defined for FDT in windows registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\FDT\DTMCatalogUpdates] *)
*) HKEY_LOCAL_MACHINE allows DTMs to write a registry key and string. During DTM setup user has to have Administrator rights anyway, so there is no missing right. While Frame session, a user can have normal rights. A Frame must only read the registry key so the missing right is not a problem. Instead of setting this attribute to optional , its mandatory and allowed to set an empty string. This avoids having old comment together with new flag.


Key Format Description
ModificationComment REG_SZ (String Value) Mandatory Any string, e.g.: Timestamp of modification. Empty string allowed.
ModificationFlag REG_SZ (String - GUID) Mandatory GUID created by DTM setup during setup runtime.

Frame Applications may update an DTM Library and save the last known ModificationFlag entry internally. A Frame can easily check if there is a need to update the DTM Catalog by comparing last known entry with current entry.

Comment:
It was seen as acceptable to leave the entry in registry without a concept for a cleanup because there may be a number of Frame Applications installed on one PC. Frame Applications are only allowed to read these keys. DTMs must update ModificationFlag and ModificationComment during setup.



© 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.