Debug remotely
- Last UpdatedApr 08, 2026
- 1 minute read
If you do not have physical access to the computer hosting the component, you can debug the component remotely from another computer.
To remotely debug Business Logic Tier (BLT) components written in Visual Basic .NET Framework (VB.NET) or C#, the target computer must have Microsoft Remote Tools for Microsoft Visual Studio installed.
In a typical remote debugging scenario, and depending on your network security, you can log on to the system using Terminal Services Client or the Remote Desktop connection and debug processes on another project computer from that session.
To debug remotely
This process is split into two procedures.
On the computer hosting the BLT component
- Start Microsoft Visual Studio Remote Debugger as an Administrator.
Allow the Microsoft Visual Studio Remote Debugger application to communicate through Windows Defender Firewall.
- Select Tools, and then Options.
The Options dialog appears. - Configure the TCP/IP port number and the authentication mode.
On the computer hosting Microsoft Visual Studio
- Start Microsoft Visual Studio as an Administrator.
- Select Debug, and then Attach to Process.
The Attach to Process dialog appears. - From the Connection target dropdown menu, select the remote computer name and the port number (for example, ls1pdcrt1:4024).
- From the Attach to field, select Select.
A dialog appears. - Select Automatic: Managed (v4.6, v4.5, v4.0) code.
- Select OK.
- Select the BLTHost process that is hosting your application.
- Select Attach.
Microsoft Visual Studio attaches to the process. - To set a breakpoint in your code, use the debugger.
- To stop debugging, without stopping the BLTHost process, select Debug, and then Detach All.