Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Former Member Absent Member.
Absent Member.
148 views

[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.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.