Starting to Debug a .NET COBOL Application in a Container

Note: The information in this topic applies to both native COBOL and .NET COBOL applications unless specifically indicated. If you want to use native COBOL in containers, however, Micro Focus recommends using the IDE-based functionality described in Debugging and Running Native COBOL Applications in Containers as it offers an fully-integrated, easy-to-use debugging experience.

Once your Enterprise Developer Build Tools for Windows base image is running and you have found out its ID or IP address you are ready to use Enterprise Developer to connect to the container using remote debugging.

Remote Debugging of Native COBOL Applications contains information about using Enterprise Developer to remotely debug native COBOL applications in general. You should be familiar with the information presented in Remote Debugging of Native COBOL Applications before learning how to use remote debugging to debug a COBOL application running in a container.

If you have followed the steps outlined in Building a .NET COBOL Application that is to be Debugged in a Container, Running a Container that is to be Debugged and Finding the Details of a Container that is to be Debugged you will have a container that isn't yet running your COBOL application but is waiting for you to connect to it using Enterprise Developer. See To start debugging a .NET COBOL application that is not yet running in a container for full information on how to do this.

Note: If you have a debuggable COBOL application that is already running in a container you can still connect to the application and debug it. See To start debugging a .NET COBOL application that is already running in a container for more information on how to do this.