Remote Tools For Visual Studio 2019

0 views

Skip to first unread message

Damaris

unread,

Aug 5, 2024, 8:03:48 AM8/5/24

to wouncisitu

Youcan run the remote debugger by copying msvsmon.exe to the remote computer, rather than installing the remote tools. However, the Remote Debugger Configuration Wizard (rdbgwiz.exe) is available only when you install the remote tools. You may need to use the wizard for configuration if you want to run the remote debugger as a service. For more information, see (Optional) Configure the remote debugger as a service.

The remote computer and the Visual Studio computer must be connected over a network, workgroup, or homegroup, or else connected directly through an Ethernet cable. Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.

You can find the remote debugger (msvsmon.exe) on a computer with Visual Studio Community, Professional, or Enterprise already installed. For some scenarios, the easiest way to set up remote debugging is to run the remote debugger (msvsmon.exe) from a file share. For usage limitations, see the remote debugger's Help page (Help > Usage in the remote debugger).

For command line installation and command line reference, see the Help page for msvsmon.exe by typing msvsmon.exe /? in the command line on the computer with Visual Studio installed (or go to Help > Usage in the remote debugger).

If you don't have administrative permissions on the remote computer, right-click the Remote Debugger app and select Run as administrator. Otherwise, just start it normally.

If you are planning to attach to a process which is running as an administrator, or is running under a different user account (such as IIS), right-click the Remote Debugger app and select Run as administrator. For more information, see Run the remote debugger as an administrator.

Select at least one network type you want to use the remote tools on. If the computers are connected through a domain, you must choose the first item. If the computers are connected through a workgroup or homegroup, choose the second or third item as appropriate.

You can run the remote debugger under a user account that differs from the user account you are using on the Visual Studio computer, but you must add the different user account to the remote debugger's permissions.

You can choose to run the remote tools in No Authentication mode, but this mode is strongly discouraged. There is no network security when you run in this mode. Choose the No Authentication mode only if you are sure that the network is not at risk from malicious or hostile traffic.

Find the Remote Debugger Configuration Wizard (rdbgwiz.exe). (This is a separate application from the Remote Debugger.) It is available only when you install the remote tools. It is not installed with Visual Studio.

Select the type of network that you want the remote tools to communicate with. At least one network type must be selected. If the computers are connected through a domain, you should choose the first item. If the computers are connected through a workgroup or homegroup, you should choose the second or third items. Click Next.

If the service can be started, you will see You have successfully completed the Visual Studio Remote Debugger Configuration Wizard. If the service cannot be started, you will see Failed to complete the Visual Studio Remote Debugger Configuration Wizard. The page also gives some tips to follow to get the service to start.

You should be able to debug your code with the symbols you generate on the Visual Studio computer. The performance of the remote debugger is much better when you use local symbols. If you must use remote symbols, you need to tell the remote debugging monitor to look for symbols on the remote machine.

Unfortunately, MS block workable link to download VS_RemoteTools_X86 for VS2019 and redirect this link to advertising of Visual Studio 2022. I don't need new Windows, new Visual Studio, new Framework, new Visual Studio for MAC or something other. I need exactly Visual Studio 2019 remote debugger tools, but unfortunately can not found it in MS site. Attempt to install msvsmon.exe to remote machine from local directory with VS2019 was unsuccessful too. And link to repair this issue Microsoft also has been break and also has redirected to meaningless advertising.

After sending them a support ticket, telling them I can not download this required software with the "perpetual free license" that I have... They tell me I can not download this, and that they really wish they could call me and turn me into a sales target.

I had some backup installers from July 2023. All Remote Tools, Team Explorer, Test Agent, Test Controller and Intellitrace Collector installers had been uploaded to: Archive.org, I hope it might help.

From the Visual Studio downloads page scroll to the bottom where you'll see a link for Older downloads. Yes, there's another prompt to install VS 2022 but look further down the page is a section for "2019", expand that and you will see download button/link for "Visual Studio 2019 and other Products". The blurb even mentions Remote Tools for Visual Studio 2019 (underlined in red below by me).

Follow that link (you'll have to sign in) and you'll be taken to a downloads page with a pre-filled search for "Visual Studio 2019". Modify the search "Visual Studio 2019 remote" and it should be easy enough to find.

To guarantee a seamless remote debugging experience for users, you need some additional dependencies to be copied to the target machine. Luckily, we do that for you and automatically deploy these dependencies alongside the built binaries from your project we deem as needed for debugging. In Windows scenarios specifically, we automatically deploy the Universal CRT library (debug only, as the release version ships with the Windows operating system) as well as VCRuntime libraries which are necessary to run and debug binaries in environments where these libraries are not available on the system.

Note: Although with Visual Studio 2019 you can create MSBuild and CMake projects targeting Linux and Windows, CMake is encouraged for Linux development because the same project files can be used in both platforms.

You can deploy and debug MSBuild projects targeting a remote Windows machine very easily in Visual Studio 2019. In the Property Pages, within the Debugging tab, you will need to specify Remote Command, Working Directory, Remote Server Name and Deployment Directory properties as a minimum. If you want to deploy additional files, you will have to specify them in the Additional Files to Deploy property.

Visual Studio 2019 has support for deploying CMake projects to a remote Windows machine and debugging them with the Visual Studio remote tools. You can specify the type and remoteMachineName properties within the launch.vs.json file.

Visual Studio 2019 allows you to specify both debug and release versions of the runtime libraries. To do so, you must set the deployDebugRuntimeLibraries and deployRuntimeLibraries properties to true.

The contents of the project outputs will be deployed automatically to C:\Windows Default Deploy Directory\ in the remote machine. If you want to specify a different location, you can set it up in the deployDirectory property. If you do not want to deploy files at all, you can set disableDeploy to true.

In addition, you can specify individual additional files or entire directories you want to deploy each time in case there are some external source/content files you want to be deployed. To do this, you add the following block to your launch.vs.json (make sure you replace example.cpp/exampleDirectory with the actual path to your file/directory):

When targeting Linux using CMake, you can specify a different machine from your build machine (the default) to deploy to and debug on. To do this, just set the remoteMachineName json filed to one of the established connections in the Connection Manager (IntelliSense will populate the list of all the available options).

I then run my run_tests.py script to start the process, it will hold for the debugger to attach. At this point, I go to the VS code debug tab and hit play. At this point the VS code breakpoints will work from the GUI from all of my sub Libraries that are utilized by my test suites. Great to step through everything in the back end.

I currently have my launcher.json file configured like so:

Does anyone know how I could configure this extension for this scenario like I am for python backend to debug my robot cases/custom keywords? Would be a great bonus if I could step into the robot keywords directly to the implementation in the python backend. Would be happy if it only worked on robot side as well. Thanks in advance all.

To the main question, I can already debug the python code. For my specific situation, I must always use the run_tests.py utility to start my robot tests on my specific device under test, as I am testing physical hardware and its capabilities. The hardware must be connected to first before robot is started, which means I cannot go into any specific robot file and just press the green arrow to run a test case. I need to use run_tests.py to start my testing no matter what.

Using debugpy, I can add a listener on port 5678 and configure the python debugger as I describe above in order to attach to the python debug process. This works great for my needs. I can put breakpoints in the IDE in any python library that is called in robot and can debug that in the backend. This has nothing to do with RobotCode extension at the moment.