Does anyone know of any restrictions or issues with using Report Writer in managed COBOL? Does anyone have any experience with Report Writer in managed COBOL?
We've converted a number of our "batch" COBOL programs to managed code with success, but this is the first one that uses Report Writer and an exception is being thrown at the C# call to COBOL class (within a rununit) that reminds me of Net Express errors I saw YEARS ago when a compiler bug created bad references that wouldn't link.
The exception is "Method not found: 'Void COBOLPrograms.WYE39P._MF_IMPLICIT_1()'".
We are running VC 2.3.1 for VS 2013 Update 5. COBOLPrograms is the COBOL class library targeting .NET Framework 4.5 with Debug/Any CPU configuration. WYE39P is the converted COBOL program (public) with only the Linkage Section and Procedure Division code residing in the single Method-ID named InstanceMethod.
We aren't getting any compile errors. And we haven't run it from a server, just within the IDE.
Questions? Comments? Ideas?
↧