Skip to main content

Debugging in Visual Studio 2017 (Enterprise Developer 3.0)

  • July 12, 2018
  • 2 replies
  • 0 views

I recently installed Visual Studio 2017 and Microfocus Enterprise Developer 3.0.

When debugging our application, which is a managed application (mixture of C# and Cobol compiled for .NET), I can't see the values of Cobol data items. The error message I get is: error CS0103: The name 'AFD2' does not exist in the current context.

To be clear, the results of the run are 100% correct, so it's seems to be a debugging issue exclusively.

I suspect that I have a wrong setting somewhere.

Kind regards,

Mark de Vos

2 replies

Fano Razafinimanana

I recently installed Visual Studio 2017 and Microfocus Enterprise Developer 3.0.

When debugging our application, which is a managed application (mixture of C# and Cobol compiled for .NET), I can't see the values of Cobol data items. The error message I get is: error CS0103: The name 'AFD2' does not exist in the current context.

To be clear, the results of the run are 100% correct, so it's seems to be a debugging issue exclusively.

I suspect that I have a wrong setting somewhere.

Kind regards,

Mark de Vos

This is the Visual COBOL forum. You should instead post your question at the Enterprise Developer forum


Gael Wilson
Forum|alt.badge.img
  • Rocketeer
  • July 13, 2018

I recently installed Visual Studio 2017 and Microfocus Enterprise Developer 3.0.

When debugging our application, which is a managed application (mixture of C# and Cobol compiled for .NET), I can't see the values of Cobol data items. The error message I get is: error CS0103: The name 'AFD2' does not exist in the current context.

To be clear, the results of the run are 100% correct, so it's seems to be a debugging issue exclusively.

I suspect that I have a wrong setting somewhere.

Kind regards,

Mark de Vos

Mark,

If you go to the Tools menu, select Options... then go to Debugging -> General and find the option named 'Use Managed Compatibility Mode'. If you check that option you should then be able to query the values of your COBOL data items.

Gael