Natural into C# Transformation
Demystify the migration process with a step-by-step look at the way Natural can be transformed into working, maintainable C# code. Why Migrate Your Mainframe?
High (and continuously increasing) maintenance and runtime fees for the existing Natural products
The shrinking availability of Natural developers and lack of interest in Natural from new developers
Lack of an easy transition path from the mainframe version of Natural to its Linux, Unix, and Window
C# offers answers to all of the above concerns:
- Maintenance and support fees are negligible when compared to Natural (or even nonexistent depending on the choices made);
- Even though there is no one universally accepted barometer to measure the popularity of the various programming languages, there is no denying that C# is considered to be one of the most widely-used programming languages today. In addition, the design of C# aims for programmer portability, for the vast range of developers familiar with C, C++, and Java;
- Even though C# has been developed by Microsoft, the product and its documentation are publicly available on the Internet (the first versions were even ISO/IEC and ECMA standards). For example, the language specification is available on the Microsoft website here.
Next to that, moving to C# also means:
- Enabling the use of a state-of-the-art IDE, with extensive debugging, refactoring, profiling and (unit)testing support.
- Enabling the use of thousands of (third-party) libraries, covering almost all imaginable computing needs: database interaction, mail/ftp/http/… communication, parsing, xml processing, …
- Enabling the use of modern application architectures including the use of an application server, web front‑ends, SOA, cloud-deployment,...
Send me the whitepaper
Thank you! Please wait redirecting...