THE MOTIVATION TO LEARN ABOUT COBOL AND VSCODE. TILL NOW I ONLY USED VSCODE AS EDITOR BUT NOW I CAME TO KNOW MORE ABOUT IT.
What it does AND ## How I built it
This augmentation was initially planned for giving linguistic structure featuring to COBOL yet the additional time it has been stretched out to give grammar featuring other related dialects/record arrangements such as JCL, PL/I, and Micro Focus order documents and Micro Focus Unit Test Reports.
This expansion is absolutely not an Integrated Development Environment for COBOL. It gives enough usefulness to the easygoing designer to see, alter, and incorporate source code (through undertakings and issue matches).
Visual Studio Code has two different ways of giving language expansions, one if through the language worker convention and the second is by means of a lot of Visual Studio Code APIs.
This augmentation utilizes the Visual Studio Code APIs in light of the fact that the Language Server Protocol didn't exist when this expansion was made.
Everywhere Visual Studio Code works.. aka Windows, Linux, and Mac OSX.
Challenges I ran into
Visual Studio code can be set up to build your COBOL source code. MsBuild based projects can be consumed as build tasks, allowing navigation to error/warnings when they occur. Single file compile using Micro Focus COBOL - ERRFORMAT(3) ingle file compile using Micro Focus COBOL - ERRFORMAT(2)
Accomplishments that I'm proud of
What I learned
THE FUNCTIONING OF VSCODE AND USAGE OF COBOL
What's next for COBOL-vscode
NOT YET DECIDED, MAYBE ANY UPDATES WOULD BE DONE.