VS 2019 client, VS 2017 web server

Jeff A. King 21 Reputation points
2021-02-22T22:57:56.36+00:00

My project resides on the web server, where only VS 2017 is installed. We just purchased a VS 2019 subscription, and installed only on my Workspace to test how each project responds to the new version. When I open and run the project in my Workspace session, using VS 2019, I get a remote debugging error (see attached). I discovered the path to the Remote Debugger (MSVSMON.EXE) is clearly different between the two versions of Visual Studio. I would expect that is the problem; when I run/build the project from my session using VS 2019, it's looking for the MSVSMON.EXE file, in the location that version VS 2019 says it exists. However, the VS 2017 location of this file is quite different. 70819-remotedebuggingerror.png

The plan is to update to VS 2019 on the server, where the project lives, but we need to make sure all of our projects will open and compile in the new version before installing it on the server.

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,604 questions
Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
938 questions
0 comments
Accepted answer
  1. Dylan Zhu-MSFT 6,406 Reputation points
    2021-02-23T07:04:22.093+00:00

    Hi JeffAKing,

    According to this error, you can have following methods to troubleshoot it before updating to VS2019:

    • Reinstall remote debugger tool on web server
    • Make sure the correct ports in the firewall are open, especially if you are using a third party firewall.
    • If you are using a HOSTS file, make sure it is configured correctly. For example, if debugging using F5 (instead of Attach to Process), the HOSTS file needs to include the same project URL as in your project properties, Properties > Web > Servers or Properties > Debug, depending on your project type.

    Best Regards, Dylan

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our * *documentation* to enable e-mail notifications if you want to receive the related email notification for this thread.**

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jeff A. King 21 Reputation points
    2021-02-23T11:50:04.78+00:00

    DylanZhu,

    Thank you for your response. Help me fully understand what you're suggesting... Are you saying I need to install the VS 2019 remote debugger tool on the web server, and then I will be able to debug from my session?

    Would my problem be solved if we just installed VS 2019 on the remote server? Our ultimate goal is to upgrade to 2019.

    I believe there is some concern that the upgrade installation on the remote server would create issues with the other existing projects located there.

    Thank you,

    Jeff.

  2. Jeff A. King 21 Reputation points
    2021-02-23T12:11:06.037+00:00

    Additionally, if we were to install the VS 2019 remote debugging tool on the web server, would this negatively impact anyone debugging a project from VS 2017?

    0 comments