Previous Topic Next topic Print topic


Visual Studio IDE

Support for COBOL in Visual Studio has been enhanced in the following areas:

  • The Go To location and Go To Procedure Division commands are now available from the Edit menu. In addition, the Go To Procedure Division has a shortcut key - Ctrl+K, Ctrl+J.
  • Object Browser - now provides support for .NET COBOL code. You can view the members of objects in your project and the definition of classes and methods as specified by the XML documentation comments in your code. The window also provides support for the Go To Definition command.
  • A new search option, Current COBOL Program, has been added to the Find in Files dialog box. This enables you to search in the COBOL program currently opened in the editor and in any copybooks referenced by that program.
  • Solution Explorer - a new context menu command, Add Folder to Copybook Paths, is now available for the subfolders of your projects. This enables you to add the subfolders to the copybook path of the project.

COBOL editor:

  • Line numbers - a new option for configuring the increment for the COBOL and the standard line numbers when you use Renumber and Unnumber has been added. You can specify the increment from Tools > Options > Text Editor > Micro Focus COBOL > Line Numbering.
  • Outlining - a new IDE option enables you to switch outlining in the COBOL editor on or off. See the Enable Outlining option available on the Advanced page in Tools > Options > Text Editor > Micro Focus COBOL.
  • Program breakpoints - a new context menu command, Add COBOL Program Breakpoint, enables you to set program breakpoints directly from the editor.

There are new options and new configuration pages in the IDE preferences:

  • Autocorrect - a new preferences page in Tools > Options > Text Editor > Micro Focus COBOL.

Debugging:

  • It is now possible to examine object reference data items as you are debugging native Object Oriented COBOL applications. The debug tooltip now displays the object's instance data provided that the debug information for the object's class is available.
Previous Topic Next topic Print topic