Debug clients and components
- Last UpdatedApr 24, 2025
- 1 minute read
There are several processes you can use to debug clients and components from Visual Studio.NET.
Currently, only Visual Studio .NET or the Microsoft Common Language Runtime (CLR) debugger can be used to debug C# or Visual Basic (VB) .NET Framework (VB.NET) applications (i.e. managed code). The free Debugging Tools for Windows package (included with AVEVA Enterprise SCADA and downloadable from Microsoft) cannot be used to debug these components.
While inside a Remote Desktop Connection or Terminal Services Client session, you will not be allowed to use Visual Studio.NET to debug a local process that has not been started by your session. However, you can debug any remote process using Visual Studio.NET from a Remote Desktop Connection.
Related Links
- Generate symbolic debugging information
- Determine the process ID (PID) of the Business Logic Tier (BLT) host process
- Local debugging using Microsoft Visual Studio.NET
- Verify that the debugger is installed on your computer
- Debug a Business Logic Tier (BLT) component using the Common Language Runtime (CLR) debugger
- Verify that the Visual Studio debugger is installed on your computer
- Debug a Business Logic Tier (BLT) component
- Debug RealTime using PubSub