We've just been informed that we will no longer be allowed to run our application from the console. Currently our application consists of a number of task-specific native console programs (.exe) that use SCREEN SECTIONs and ACCEPTs and DISPLAYs to gather task-specific input from the operator and then call distinct series' of individual native Dynamic Link Libraries (.dll), passing the gathered input data through LINKAGE SECTIONs. Our idea is to replace the console programs with .aspx's, and port the native .dll programs to managed code in a new solution. That way the .aspx's can gather the input data via web pages and then drive the call lists of .dlls.
We are assuming that the .dll programs will be COBOL>Managed>Class Library projects?
But when we tried to create a managed code version of one of the native .dll programs the compiler completely choked with errors and warnings. A big part of the problems seem to stem from a right margin (col. 72) not being recognized when using managed code projects?
Does anyone know of a document/check list that covers most if not all of the code changes that have to be made to 40-year-old batch mainframe-style formatted (80-column card) COBOL code to convert it to managed Class Library?