Remote debugging profile validates path to executable locally instead of remotely

[vsfeedback]

This issue has a corresponding ticket on Developer Community. Please vote and comment there to make sure your voice is heard.

---

As shown on attached screenshot: Setting up a debug profile with the "Use remote machine" option enabled and specifying a path to the executable, fails to start, because it incorrectly validates the existence of said path on the local machine instead of the remote one.

I'm able to workaround this issue by creating an empty file on the local PC that's located at the same path as the actual executable is on the remote PC. It then correctly starts a remote debugging session. But not all developers in my team are able to use this workaround, because some do not have any drive D: on their machines.

This seems to be a regression, since a while ago I had no trouble with this. I can't recall, though, the last version of VS where this was still working correctly.

---

Original Comments

Feedback Bot on 2/14/2021, 06:39 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

[jjmew]

We might not need to validate this unless you are not remote debugging. @melytc - can you sync up with @tmeschter who was some additional information.