Question about extensions compatibility
ivanpovazan opened this issue · 2 comments
Hello,
My name is Ivan Povazan and I am software engineer at Raincode.
We are currently developing a Visual Studio Code extension which would serve as a language service for developing legacy applications (COBOL, PL/I and HLASM) targeting .NET with our tools.
The extension enables users to:
- generate build and launch assets specific to our tools
- build legacy applications for .NET
- launch and debug (set breakpoint, inspect variables, etc.) legacy applications on .NET
Since you provide a widely-used and feature-rich extension for editing legacy sources, we are very interested in utilizing its syntax highlighting and IntelliSense features and making our extension depend on it.
However, we have noticed that there are conflicting contribution points for debugger and breakpoints which are detected upon bitlang.cobol activation.
Regarding this issue, we would like to know:
- What is the process of ensuring compatibility between extensions and removing the warning message?
- Are there some guidelines on how this can be achieved?
Thank you in advance
Hi @ivanpovazan,
This extension provides COBOL support for various 'Micro Focus COBOL' dialects & products, so it's natural that this extension needs to be 'partnered' with an appropriate debugger.
The purpose of the compatibility check is to ensure that the code that is being visualised by extension can be debugged.
The only known debugger that works with extension in full is the one provided by 'Micro Focus'.
I understand, thank you for the explanation.