- #Visual studio remote connection install
- #Visual studio remote connection code
- #Visual studio remote connection windows
Universal Windows App (UWP), OneCore, HoloLens, or IoT - Debug an app that you didn't start from Visual Studio See Debug an installed app package instead of using Attach to Process Universal Windows App (UWP), OneCore, HoloLens, or IoT app - Remote debug If necessary, use Resource Monitor to help identify the process. If server is remote, use remote tools, and Attach to ProcessĬhrome.exe, msedge.exe, or other processes Other supported app types - Debug on a server process See Attach to a process running in a Docker container For containerized apps, see Attach to a process running in a Docker container. See Remote debug a C# or Visual Basic app or Remote debug a C++ app In most scenarios, use standard debugging and not Attach to Process. Use either standard debugging ( F5) or Attach to Process For Chrome, you must also run Chrome in debug mode (type chrome.exe -remote-debugging-port=9222 from a command line) and select JavaScript or TypeScript in the Attach to field.Ĭ#, Visual Basic, or C++ app - Debug on the local machine See Remote debugging ASP.NET on a remote IIS computerĬlient-side script - Debug on a local IIS server, for supported app types This may be helpful to make your app load faster, such as (for example) when profiling.ĪSP.NET 4 or 4.5 - Remote debug on an IIS server For more detailed information, see Remote debugging ASP.NET Core on a remote IIS computerĪSP.NET Core - Debug on the local machine after you start the app without the debugger
NET Core 3, the w3wp.exe process is used for the default in-app hosting model. ScenarioĪSP.NET Core - Remote debug on IIS server To quickly select a running process to attach to, in Visual Studio, type Ctrl+ Alt+ P, and then type the first letter of the process name. In earlier versions of Visual Studio, the script debugger for Chrome was Web kit.
#Visual studio remote connection code
For debugging client-side script on Chrome, choose JavaScript (Chrome) or JavaScript (Microsoft Edge - Chromium) as the code type, and depending on your app type, you may need to close all Chrome instances and start the browser in debugging mode (type chrome.exe -remote-debugging-port=9222 from a command line).
#Visual studio remote connection install
To obtain tlist.exe, download and install Debugging Tools for Windows, available at WDK and WinDbg downloads.įor client-side script debugging, script debugging must be enabled in the browser. You can determine the process ID using tlist.exe. If neither of those workarounds is possible, a third option is to attach to the process by running vsjitdebugger.exe -p from the Windows command line. You can solve the problem by running Visual Studio under an administrator account or by running Visual Studio from the server console instead of a Terminal Services session. Session 0 is used for services and other server processes, including w3wp.exe. If you are running Visual Studio as a user who has a limited user account, the Available processes list won't show processes that are running in Session 0. In some cases, when you debug in a Remote Desktop (Terminal Services) session, the Available processes list won't display all available processes. You can set the active app in the Visual Studio Debug Location toolbar or Processes window. You can be attached to multiple apps for debugging, but only one app is active in the debugger at a time. Verify that Visual Studio adds the required port to the computer name, which appears in the format: :port Type the computer name in the Connection target box and press Enter. Select the drop-down arrow next to Connection target, and select the computer name from the drop-down list. In the Connection target box, select the remote computer, using one of the following methods: For more info, see other sections in this article or Common debugging scenarios. Some scenarios, such as debugging Linux or a containerized app, require a different connection type. In Visual Studio, select Debug > Attach to Process (or press Ctrl+ Alt+ P) to open the Attach to Process dialog box. To attach to a running process on a remote computer: For more information, see Remote debugging.įor more complete instructions for debugging ASP.NET applications that have been deployed to IIS, see Remote debugging ASP.NET on a remote IIS computer. The remote debugger ( msvsmon.exe) must be running on the remote computer. You can also select a remote computer in the Attach to Process dialog box, view a list of available processes running on that computer, and attach to one or more of the processes for debugging.
0 kommentar(er)
