microsoft / microsoft/vscode-cpptools

Feature Request: Remote Debugging for cppvsdbg

Open
#1,098 7 comments 27 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger Feature Request
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

I debug my applications on a Remote Test PC because I have additional hardware attached to that PC that I can't attach to my Development PC. I currently use Visual Studio to do that. I take a copy of "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x86" and run "..\Remote Debugger\x86\msvsmon.exe" on my Test PC. Then I attach to my application using VS->"Transport"->"Remote (no authentication)". No authentication connection is OK for me because I'm on a private network.
I would like to be able to do something similar with vscode so that my whole development environment is on vscode using the cpptools extension.
My application is built with an internal build environment and I can only use msvc as the compiler, so I can't switch to "cppdbg"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the cpptools extension's cppvsdbg integration and the described Visual Studio msvsmon.exe workflow. Confirm whether remote, no-authentication attachment to an MSVC application is supported; done means a VS Code session can connect to the remote Test PC and debug the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.