Debugging Configuration Files
An essential aid to understanding configuration file processing is the MicroStation PowerDraft's command line argument " -debug[=n] ". This command instructs MicroStation PowerDraft to create a text file that contains the history of how every configuration file was processed. The optional "=n" portion indicates the level of detail to put into the file. The resulting file is opened in your default text editor (usually Notepad). When you close the text editor, MicroStation PowerDraft also closes.
To start the product with the -debug=n command line argument:
- At a command prompt, enter:
Where, <installation_folder> is the path at which your product is installed ( C:\Program Files\Bentley\<product_name> CONNECT Edition\<product-name> ).
- or append
-debug=n to the Target field in the product’s
program item's properties dialog (Shortcut tab).
where n is a value from 1 to 5, with the following results:
Value of n Type of report 1 Brief report that shows the current string value of each Configuration Variable as it is processed. 2 In addition, shows the current translation of each Configuration Variable as it is processed. 3 In addition, shows conditional break information by displaying the line number when each if preprocessor directive is processed. 4 In addition, prints final translations of all Configuration Variables at the end of the report. This is the default setting. 5 In addition, shows final values of all Configuration Variables at each level (System, Application, Organization, WorkSpace, WorkSet, Role, User).
For most purposes, the value 4 (the default setting) gives the most meaningful report: It shows the values of the Configuration Variables as they exist while the product is running.
The information in the report is saved as ASCII text in the msdebug.txt file in the TMP directory. That location is reported in the text window.