DSC naming conventions
UNICOM Intelligence recommends the use of the following naming conventions for DSCs:
Component name
This is the name of the .dll file built by the Visual Basic or Visual C++ project. It should be in the form:
xxDddDsc
Where xx is an abbreviation for your company and Ddd is an abbreviation that represents the underlying data type. For example:
abcPrtDsc
mrQvDsc
Component description
This is set in the registration. Use the following format:
<company_name> <underlying_data_type> Data Source Component
For example:
ABC Parrot Data Source Component
MyCompany Quanvert Data Source Component
Case data capability class name
This is set in the registration. Use the following format:
<component_name>.Source
For example:
abcPrtDsc.Source
mrQvDsc.Source
Metadata capability class name
This is set in the registration. Use the following format:
<component_name>.<ddd>Metadata
Where <ddd> is the abbreviation for the underlying data type. For example:
abcPrtDsc.PrtMetadata
mrQvDsc.QvMetadata
Capability title
This is set in the registration. Use the following format:
<company_name> <underlying_data_type> File/Database/...
For example:
ABC Parrot .prt File
MyCompany Quanvert Database
File mask
This is set in the registration. Use the following format:
<file_description>|<filename_extension_masks>
For example:
Parrot files|*.prt; *.pts
Quanvert project files|*.pkd; qvinfo
See also