Comprehensive Guide to Using VS Code for Backend Development, Remote Debugging, and Plugin Configuration

This article presents a detailed guide for backend developers on configuring and using Visual Studio Code (VS Code) as a lightweight yet powerful IDE. It covers the motivations for choosing VS Code, compares it with other IDEs, and walks through installation, proxy configuration, language packs, remote development, and debugging setups for C++, Python, and Shell.

1. Why VS Code

Supports multiple languages (C++, Java, Python, Shell, Proto, Makefile, etc.)

Provides Vim, Sublime, Eclipse key‑binding mappings

Offers code completion, function navigation, multi‑platform usage, low memory footprint, rich plugin ecosystem, Docker and database management, unit testing, custom terminals, and LeetCode integration.

2. Comparison with Other IDEs

SourceInsight lacks GBK support and long‑path handling.

Vim becomes cumbersome for large projects.

Eclipse is heavy and consumes significant memory.

VS Code addresses these shortcomings, though it still has occasional bugs such as missing local variable definitions.

3. VS Code Installation

The editor can be downloaded from the official site (https://code.visualstudio.com/) for Windows, macOS, and Linux.

4. Configuring a Corporate Proxy

The main configuration file is settings.json. To enable proxy access for extensions, add the following entries:

"http.proxy": "http://YOUR_PROXY_IP:PORT/",
"http.proxyStrictSSL": false,

After editing, VS Code can open the JSON file via Ctrl+Shift+P → Preferences: Open Settings (JSON) .

5. Installing the Chinese Language Pack

Search for “Chinese” in the Extensions Marketplace, install the first result, and reload the window.

6. Remote Development

Install the “Remote Development” extension, reload, and then add remote machines through the small computer icon that appears on the left sidebar. SSH keys can be generated with ssh-keygen or copied using:

ssh-copy-id user@server

ssh-copy-id -i ~/.ssh/id_rsa.pub user@server

After configuring the connection, the remote workspace can be opened, and an integrated terminal (e.g., Zsh with Git plugins) will start in the project root.

7. C++ Remote Debugging

Install the C++ extension, then create a launch.json configuration (the example below satisfies most users). The configuration includes both “Attach” and “Launch” modes and requires a running gdbserver on the remote host.

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "(gdb) Attach",
            "type": "cppdbg",
            "request": "attach",
            "program": "${workspaceFolder}/bin/app ",
            "processId": "${command:pickProcess}",
            "MIMode": "gdb",
            "setupCommands": [
                {"description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true},
                {"description": "Enable print elements", "text": "-interpreter-exec console \"set print elements 0\"", "ignoreFailures": true}
            ]
        },
        {
            "name": "(gdb) Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${workspaceFolder}/bin/app ",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}",
            "environment": [],
            "externalConsole": false,
            "MIMode": "gdb",
            "miDebuggerPath": "gdb",
            "miDebuggerArgs": "gdb",
            "linux": {
                "MIMode": "gdb",
                "miDebuggerPath": "/usr/local/onlinenavi/bin/gdb",
                "miDebuggerServerAddress": "IP:PORT"
            },
            "logging": {"moduleLoad": false, "engineLogging": false, "trace": false},
            "setupCommands": [
                {"description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true},
                {"description": "Enable print elements", "text": "-interpreter-exec console \"set print elements 0\"", "ignoreFailures": true}
            ]
        }
    ]
}

After adjusting paths to your environment, start gdbserver on the remote host before launching the debug session.

8. Python Debugging

Install the Python extension, then configure the debugger through the standard VS Code UI. Remote debugging works similarly to the C++ setup.

9. Shell Debugging

Install the Shell extension, add a launch configuration, and you can debug shell scripts with breakpoints and variable inspection.

10. Git Management

VS Code includes built‑in Git UI. Custom keybindings can streamline commit, push, and other operations (e.g., Command+Enter for commit, Shift+Command+Enter for push).

11‑13. Additional Extensions

GitLens for enhanced blame view.

Git Graph for visual commit history.

Vim extension to retain Vim workflow inside VS Code.

14‑15. Docker and MySQL Development

Docker extension enables container management directly from the IDE; MySQL extension provides database browsing and query execution.

16‑18. Miscellaneous

Add useful .gdbinit snippets for better gdb output.

Customize the integrated terminal (e.g., Zsh) via settings.

Install the LeetCode extension to solve coding problems without leaving VS Code.

Overall, this guide equips backend developers with a fully configured, lightweight IDE that supports remote development, multi‑language debugging, version control, containerization, and productivity‑boosting extensions.