You can use
Enterprise Developer installed locally to debug a .NET COBOL application running on a remote Windows machine.
Note: This is only supported with
Enterprise Developer for Visual Studio 2017 and later because it uses the new Visual Studio debug engine. The remote application must run on Windows.
To prepare for debugging
Ensure that you have the following installed on your local machine:
- Enterprise Developer for Visual Studio 2017
- The application's project file or symbols (either .idy or .pdb). You do not need these files if you are going to use
Attach to Process.
- Establish a connection between your local machine and the remote one -
click here for instructions.
Ensure that you have the following on the remote Windows machine:
To debug a .NET COBOL application remotely
These are the instructions to debug an application that runs on a remote machine:
- On your local machine, start Visual Studio.
- Either create a new .NET COBOL project or open the one that was used to create the application you want to debug.
- Configure your project for debugging:
- Navigate to the project's properties and click the
Debug tab.
- Under
Start Action, specify the
Start project.
- Under
Start Options, check
Use remote machine and specify the name (or the IP) and the port number of the remote machine as used by the Remote Debugger - such as
machinename:4022.
- On the remote machine, create a folder structure to match the path to the
bin\Debug folder of the application on your local machine.
- Copy the application's binary files to that folder.
- Start Microsoft's Remote Debugger application on the remote machine -
click here for instructions.
- Start debugging in Visual Studio on your local machine.