Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Microsoft Visual Studio 2019 Remote Debugger Download
6 views
Skip to first unread message
Jaimee Beichner
Jan 2, 2024, 5:36:12 PM1/2/24
to
If you do a Google search, you will find that this is because the remote computer cannot connect back to the desktop for some reason. By the error it's obviously an authentication issue. Most articles point to making sure that the account the remote debugger is on also has access to the client machine. I am using the same account which is local administrator on both, so that is not the issue.
This question might be misunderstood. I am not sitting at the computer where Microsoft SQL Managment studio resides and I am attempting to debug a remote database. That is not the issue I am having at all. Instead, I have remoted into a client's server by their request and also I am trying to debug an issue they are having. You see, this is how things are evolving in our world. More and more there are situations where a developer is working from home and has to remote into a client's system do get some work done.
microsoft visual studio 2019 remote debugger download
Download https://t.co/cugCgWiTzo
[3] Visual Studio 2012 and 2013 both have the display name of the installed service as "Remote Debugger", although their service names are different. This causes conflict when installing remote debugger service for 2012 and 2013 at the same time. Rename the display name (DisplayName is the value name in registry) of one in registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msvsmon120 is the key for VS2013, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msvsmon110 for VS2012), reboot, and reinstall/repair the installation of the other to fix this.
You can terminate the entire debugging session (both the remote and local debugger instances) from the remote machine using the qq command. By contrast, the q command terminates only the remote instance and leaves the local debugger instance intact.
In addition to their obvious benefits in remote debugging scenarios, WinDbg remote sessions can be useful even when debugging on the same machine. An example is when you start debugging using one of the command-line Windows debuggers (cdb.exe or ntsd.exe) and later decide to switch to using WinDbg as a front-end UI to that same session.
You can use remote stubs in both user-mode and kernel-mode remote debugging with the Windows debuggers. The dbgsrv.exe process, which comes as part of the Windows debuggers package, is used as a stub process in remote user-mode debugging. The kdsrv.exe process, also included in the Windows debuggers package, is used in remote kernel-mode debugging.
The dbgsrv.exe stub process is running in the background at this point. Using the netstat.exe tool that comes with Windows under the system32 directory, you can display the open network ports on the machine and confirm that this stub process is listening for connections from a remote debugger on TCP port 4445:
After you connect to the remote stub, you can attach to processes running on the target machine by using the familiar File\Attach To A Process menu command (the F6 shortcut). However, this option now shows processes from the target machine, which is exactly what you want in this case. Once attached to a process, you can debug it as if it were running locally, with symbols and debugger extensions located relative to the same remote debugger machine (and not the target machine, as was the case in remote sessions).
When you no longer need the remote debugging channel, make sure you terminate the stub process on the target machine so that you release the TCP port it opened earlier for other uses on the machine. You can do that in the Windows task manager UI or by using the kill.exe command-line utility from the Windows debuggers package.
This same approach can be used for remote kernel-mode debugging, except you should use the kdsrv.exe stub instead of the dbgsrv.exe stub. Note that in that case, there are actually three machines involved: the regular target and host kernel debugger machines, and the remote machine you are using to run the debugger instance. The kdsrv.exe process is started as a remote stub on the kernel host debugger machine, not the target machine that is being debugged with the kernel debugger. Symbols and extensions are again resolved relative to the remote debugger machine.
Unlike native code symbols, which are resolved in Visual Studio remote debugging relative to the remote machine (as was the case in the WinDbg stub-based remote debugging case), managed-code symbols are resolved relative to the target machine because of the in-process nature of managed-code debugging. Keep this in mind when you use Visual Studio and you want to perform remote source-level debugging of .NET applications because you need to copy the symbols to the target machine for the debugger to locate them successfully.
Remote Debugging feature requires certain inbound ports to be opened for the Visual Studio remote debugger within your Microsoft Azure App Services web applications configuration. Implementing the principle of least privilege by closing the access to these inbound ports will help you significantly reduce the possibility of a security breach.
To debug your app, you can use remote debugging, which is fully supported on ARM64. The download and instructions can be found at Remote Debugging on docs.microsoft.com. You can also create a package for sideloading or directly copy binaries over to a Windows 10 on ARM device to run your app.
So, using the Visual Studio Debugger makes this all a lot harder than the ideal case where you could simply have all of your VMs running the remote debugger service and then seamlessly connect to debug them.
The first time you start the remote debugger or before you have configured it, the Remote Debugging Configuration dialog box appears. Click the Configure remote debugging button.
On the development machine where Visual Studio is installed, you can manually attach the debugger to the remote server where the extension is running. Once the remote debugger is set up on the server machine, follow these steps to attach the debugger to the service remotely:
First, we create an Amazon EC2 instance from a base Elastic Beanstalk image. Next, we install Visual Studio remote debugger as a service and create a custom image from it. Then, we start an Elastic Beanstalk environment with this custom image. To allow communication with the Visual Studio remote debugger, we set up proper security groups. Finally, we attach the Visual Studio debugger to the remote process running inside the EC2 instance started by Elastic Beanstalk.
Note: If you do not want to create a custom image another approach you can use to install the Visual Studio remote debugger is to use .ebextensions. As detailed in Customizing Software on Windows Servers an .ebextension file can include commands that can run the installation when Elastic Beanstalk deploys the application.
Developers can now debug on their production machines with no development tools installed other than the remote debugger, they can target less common developer environments as well as environments where Visual Studio is unavailable.
35fe9a5643
This question might be misunderstood. I am not sitting at the computer where Microsoft SQL Managment studio resides and I am attempting to debug a remote database. That is not the issue I am having at all. Instead, I have remoted into a client's server by their request and also I am trying to debug an issue they are having. You see, this is how things are evolving in our world. More and more there are situations where a developer is working from home and has to remote into a client's system do get some work done.
microsoft visual studio 2019 remote debugger download
Download https://t.co/cugCgWiTzo
[3] Visual Studio 2012 and 2013 both have the display name of the installed service as "Remote Debugger", although their service names are different. This causes conflict when installing remote debugger service for 2012 and 2013 at the same time. Rename the display name (DisplayName is the value name in registry) of one in registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msvsmon120 is the key for VS2013, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msvsmon110 for VS2012), reboot, and reinstall/repair the installation of the other to fix this.
You can terminate the entire debugging session (both the remote and local debugger instances) from the remote machine using the qq command. By contrast, the q command terminates only the remote instance and leaves the local debugger instance intact.
In addition to their obvious benefits in remote debugging scenarios, WinDbg remote sessions can be useful even when debugging on the same machine. An example is when you start debugging using one of the command-line Windows debuggers (cdb.exe or ntsd.exe) and later decide to switch to using WinDbg as a front-end UI to that same session.
You can use remote stubs in both user-mode and kernel-mode remote debugging with the Windows debuggers. The dbgsrv.exe process, which comes as part of the Windows debuggers package, is used as a stub process in remote user-mode debugging. The kdsrv.exe process, also included in the Windows debuggers package, is used in remote kernel-mode debugging.
The dbgsrv.exe stub process is running in the background at this point. Using the netstat.exe tool that comes with Windows under the system32 directory, you can display the open network ports on the machine and confirm that this stub process is listening for connections from a remote debugger on TCP port 4445:
After you connect to the remote stub, you can attach to processes running on the target machine by using the familiar File\Attach To A Process menu command (the F6 shortcut). However, this option now shows processes from the target machine, which is exactly what you want in this case. Once attached to a process, you can debug it as if it were running locally, with symbols and debugger extensions located relative to the same remote debugger machine (and not the target machine, as was the case in remote sessions).
When you no longer need the remote debugging channel, make sure you terminate the stub process on the target machine so that you release the TCP port it opened earlier for other uses on the machine. You can do that in the Windows task manager UI or by using the kill.exe command-line utility from the Windows debuggers package.
This same approach can be used for remote kernel-mode debugging, except you should use the kdsrv.exe stub instead of the dbgsrv.exe stub. Note that in that case, there are actually three machines involved: the regular target and host kernel debugger machines, and the remote machine you are using to run the debugger instance. The kdsrv.exe process is started as a remote stub on the kernel host debugger machine, not the target machine that is being debugged with the kernel debugger. Symbols and extensions are again resolved relative to the remote debugger machine.
Unlike native code symbols, which are resolved in Visual Studio remote debugging relative to the remote machine (as was the case in the WinDbg stub-based remote debugging case), managed-code symbols are resolved relative to the target machine because of the in-process nature of managed-code debugging. Keep this in mind when you use Visual Studio and you want to perform remote source-level debugging of .NET applications because you need to copy the symbols to the target machine for the debugger to locate them successfully.
Remote Debugging feature requires certain inbound ports to be opened for the Visual Studio remote debugger within your Microsoft Azure App Services web applications configuration. Implementing the principle of least privilege by closing the access to these inbound ports will help you significantly reduce the possibility of a security breach.
To debug your app, you can use remote debugging, which is fully supported on ARM64. The download and instructions can be found at Remote Debugging on docs.microsoft.com. You can also create a package for sideloading or directly copy binaries over to a Windows 10 on ARM device to run your app.
So, using the Visual Studio Debugger makes this all a lot harder than the ideal case where you could simply have all of your VMs running the remote debugger service and then seamlessly connect to debug them.
The first time you start the remote debugger or before you have configured it, the Remote Debugging Configuration dialog box appears. Click the Configure remote debugging button.
On the development machine where Visual Studio is installed, you can manually attach the debugger to the remote server where the extension is running. Once the remote debugger is set up on the server machine, follow these steps to attach the debugger to the service remotely:
First, we create an Amazon EC2 instance from a base Elastic Beanstalk image. Next, we install Visual Studio remote debugger as a service and create a custom image from it. Then, we start an Elastic Beanstalk environment with this custom image. To allow communication with the Visual Studio remote debugger, we set up proper security groups. Finally, we attach the Visual Studio debugger to the remote process running inside the EC2 instance started by Elastic Beanstalk.
Note: If you do not want to create a custom image another approach you can use to install the Visual Studio remote debugger is to use .ebextensions. As detailed in Customizing Software on Windows Servers an .ebextension file can include commands that can run the installation when Elastic Beanstalk deploys the application.
Developers can now debug on their production machines with no development tools installed other than the remote debugger, they can target less common developer environments as well as environments where Visual Studio is unavailable.
35fe9a5643
0 new messages