HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Micro Focus\Visual COBOL\2.3\ADDONS
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Micro Focus\Visual COBOL\2.3\ADDONS\MyCompany
In this example, the key should be 1.0:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Micro Focus\Visual COBOL\2.3\ADDONS\MyCompany\1.0
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Micro Focus\Visual COBOL\2.3\ADDONS\MyCompany\1.0\PreProcessor
Registry entry | Value | Description |
---|---|---|
PP_01 | P(path\mypreprocessor.ext) | Where path\mypreprocessor.ext is the full path to the executable file for your preprocessor. |
PPName_01 | PreprocessorName |
The name of the preprocessor as it should appear in Enterprise Developer. For example: “XYZ preprocessor”. |
PPOptions_01 | Preprocessor arguments |
Arguments to pass to the preprocessor when it is selected in Enterprise Developer. Optional (you do not need to specify PPOptions_01 if the preprocessor does not take any arguments). For example, the XYZ preprocessor might recognize “-r -s” as valid arguments. |
PPExtension_01 | ext | File extensions that should be treated as COBOL by Enterprise Developer so they are recognized as a valid resource for the COBOL Compiler. Optional. |
PPBGP_01 | 1 or 0 | A Boolean to specify if background parsing is supported (1) or not (0). |
In our example, your registry entries look as follows:
This is how you can select your preprocessor in the project properties in Enterprise Developer