Write a Proxy or Edit the COBOL for .NET Interoperation?

If the COBOL types are incompatible with the managed non-COBOL you want to interoperate with, you can either re-engineer the existing COBOL, or write a proxy COBOL class to act as an interface between the existing COBOL and the non-COBOL.

These two options have the following implications:

The advantages of calling the COBOL directly are:

The advantages of using a proxy class are: