Thanks Brett, that's very helpful. Have tried out the various combinations of VS Code import and export of code and also $SYSTEM.OBJ.Load() / .Export() / .ExportUDL() and what we are seeing matches your description. I suspect we'll never know how the affected classed got into our codebase in the first place, but now that we know what's going on we can make some attempt to manage the situation.

Thanks for replying:

1. Not really what @Brett Saviano, one of the ISC maintainers of the VS Code extension, said in previous discussion on the extension's github page.
2. Yup
3. But how? Try and edit, using either Studio or VS Code, to produce a '//XXX' comment (no space) outside a method definition. You can't do it - the space is generated by the editors without your intervention. Hence my question - how did that space get into Ensemble in the first place?
4. Yup
5. In principle its not just commented out Property's, it seems to be any '//' comment with no space after the '//' when that comment is not within a method (or classmethod) definition. And finding the couple of hundred classes with such comments across a 4000 class file production is a non-trivial exercise!

Sorry, should have linked earlier discussions:

• VS Code ObjectScript extension error | InterSystems Developer Community |
• Request textDocument/documentSymbol failed. Error: name must not be falsy · intersystems-community/vscode-objectscript · Discussion #1530