dlls directly from C# or managed COBOL using Platform Invoke (P/Invoke).īecause of the data type differences between C# and unmanaged COBOL it is usually easier to create a proxy wrapper program in managed COBOL which actually does the call to the unmanaged code.Ĭ# would instantiate the COBOL wrapper and pass it. If you are using Visual Studio 2010 for your C# development then perhaps you should look at the Visual COBOL 2010 product as it integrates with VS2010 instead of VS2008. NET component and license during the product install. You can create both unmanaged 'native' applications using SEE 6.0 as well as managed code COBOL applications if you installed the. There really is no Net Express 6.0 product, the official name would be Studio Enterprise Edition 6.0 which installs into Visual Studio 2008. Than I would have to add a reference to this proxy class in my c# client application.ġ] If you could provide feedback on the above assumptions and questions that would b greatly appreciated.Ģ] Can I create these proxy classes using c# code? or, is the easy way to use cobol proxies on this side?ģ] If i want to call a method in C# class (assembly) how can this be completed from the native cobol/ side? From my reading on the proxy classes it would make sense to compile the proxy to an assembly. However, I don't know much about the whole mirco-focus environment. I would assume that with Net Express 6.0 and or Visual Studio (2008/2010) we can create these proxy classes in.

It apprears that the best way to do this by creating proxy classes to interact with the native cobol procedures. I need to interact with the cobol code (native cobol) with c# code (assemblies). We seem to have Net Express 6.0 on several Cobol developers machines. I believe we have a MF cobol environment converted to run on SQL server.

Ok, first off I'm not 100% sure of the Micro Focus enviroment and have not code much COBOL and that as 14 years ago.

Microfocus netexpress free download