Using the hash character (#) in configuration files and command line files

The command file template states "Lines that start with the '#' character are treated as comments and ignored". It does not contain the word "Only".

Anything to the right of the hash character (#) is not processed. So if the hash character (#) is at the beginning of a line, the entire line (everything to the right) does not get processed. If the hash character (#) is in the middle of the line, the beginning of the line up to the hash character (#) will be processed and everything after (to the right) of the hash character (#) does not get processed.

Unknown said:

Anything to the right of the hash character (#) is not processed. So if the hash character (#) is at the beginning of a line, the entire line (everything to the right) does not get processed. If the hash character (#) is in the middle of the line, the beginning of the line up to the hash character (#) will be processed and everything after (to the right) of the hash character (#) does not get processed.

As far as I am aware it has been that way at least since v7. I have config files that have # symbols in the middle of lines to denote definitions for what is on each line.

So the v7 is still a gold standard ignoring that much has changed and there is no longer only 63 levels.

We have some level names containing hash character so it is not possible to do batch processing with level names and it is not invalid character.

"Level name cannot have one or more of the following invalid characters - <>\/."?*|,='&"

Oto said:

We have some level names containing hash character so it is not possible to do batch processing with level names

That merits a new thread: "How do I batch process DGN files that contain levels that have the hash (#) character in the level name?"

Not really, created another service ticket.