VS code vs Eclipse to create CDS views

While VS Code is a very popular and versatile code editor, it currently cannot fully replace Eclipse with ADT for ABAP CDS view development. Here's a breakdown of the limitations and potential workarounds:

Why VS Code falls short (for now):

• ABAP-Specific Features: VS Code lacks the deep integration with the ABAP development environment that Eclipse with ADT provides. This includes features like:
  • ABAP Syntax Highlighting and Code Completion: While you can get basic SQL highlighting in VS Code, it won't have the specialized ABAP CDS syntax support.
  • Data Dictionary Integration: Direct access to the ABAP Data Dictionary (DDIC) for browsing tables and structures is crucial for CDS development, and this is not readily available in VS Code.
  • Activation and Transport: Seamlessly activating CDS views and managing transports within the ABAP system is a core function of ADT, which is not present in VS Code.
  • Debugging: Debugging CDS views within the ABAP context is much easier within the ADT environment.
• Backend Connection: VS Code doesn't have the same level of direct connectivity to ABAP backend systems that Eclipse with ADT offers. This makes it difficult to work with CDS views that are tightly coupled to the ABAP layer.

Potential Workarounds (with limitations):

1. Code Editing and Basic Syntax: You can use VS Code as a basic code editor for drafting the initial SQL-like structure of your CDS view. You can find extensions that provide some level of SQL syntax highlighting and code completion.
2. ABAP Remote FileSystem (Limited): If your ABAP system is configured with the ABAP Remote FileSystem (ARFS), you might be able to edit CDS view source files directly on the server using VS Code. However, you'll still lack the ABAP-specific features and integration mentioned above.
3. Hybrid Approach: Similar to the approach with BAS, you could use VS Code for initial drafting and then switch to Eclipse with ADT for the core development, activation, and testing.

Looking Ahead:

• SAP's evolving strategy: SAP is constantly working on improving its development tools and integrations. It's conceivable that in the future, VS Code might gain more comprehensive support for ABAP CDS view development. Stay updated with SAP's announcements and roadmaps.

In conclusion: While VS Code is a powerful tool for many development tasks, it's not yet a full-fledged replacement for Eclipse with ADT when it comes to ABAP CDS views. Eclipse with ADT remains the recommended environment due to its deep ABAP integration and specialized features.