[archive] suggestion .Net
[Migrated content. Thread originally posted on 25 March 2008]Hello everyone,
we're considering use a .NET component to build up a new program in an existing application: all data's must reside on Vision files due to being useful for other part of the application but graphical look and feel and operativity forces us to use a .NET component. Now we wonder to choose the right approach:
1) build a .NET program that talks to Acu for the data i/o and business logic of data's
2) build a Cobol program that includes (more than one) .NET objects and manages them?
Main app may be running on Thin environment just for performance purpose not due to remote accessibility.
Any suggestion to make the right and easier choice?
Thank in Advance, Gio.