Standardized Approach beats the alternatives

The original application architecture is preserved thereby avoiding the unnecessary risks inherent in experimenting with code changes. The basic premise is that if your code works in Team Developer, then it will work in .NET. After hundreds of migrations using our technology this premise continues to hold true.

We use many built-in and customisable refactoring techniques to transform and modernise the code and user interface without altering the original application logic and fundamental structure. Virtually no risk is added using our standardised approach.

There is no limit to what can be done with applications migrated to .NET using our technology.

The migration produces a Visual Studio project entirely based on the .NET Framework. The new application can be skinned, turned into a smart-client application, enhanced using any .NET control, re-architected to use Web Services, integrated with external systems, and so on.

Quickly achieve the sort of improvement in appearance shown above. Once a system is migrated to .NET it is easy to use Ice Porter's state-of-the-art reliable components to modernise the look and feel of an application and improve the user experience.

The bottom line is that technology will no longer be an impediment; now the focus can be on features instead of workarounds.

Let us show you what can be done with a Gupta application once it runs on Microsoft .NET. Contact us for a Free Evaluation.

Our translation process is straightforward and flexible.

Ice Porter™ loads the source SAL application using the CDK, parses all expressions into expression trees, loads and binds all known assemblies (including modules that have already been ported and custom plugins), analyses all references and relationships, re-generates the application into a CodeDOM structure (XML-Like Code Document Object Model), optimises the resulting structures, and finally feeds the final CodeDOM to code renderers that generate the final source code in a reliable and consistent manner.

Throughout the entire process, the tool generates special events that can be handled by custom-developed translation filters. Translation filters can modify and enhance the translation process at every step.

The translation technology can be adapted virtually to any requirement.

Our migration support library is called PPJ Framework™.

All migration solutions have a support library. Some may be better or more extensive than others, but all automated, semi-automated, or manual conversion approaches have one. Our happens to be the best, most standard, widely adopted, most tested and most reliable.

It's a standard library already deployed to tens of thousands of users worldwide.

Our library is entirely written in C# and it directly extends native types and native controls.

The only third party component used is the FlexGrid .NET, for which an OEM license has been obtained. The database layer in the PPJ Framework is entirely based on ADO.NET and can use any ADO.NET compliant driver.

The library is as thin and modular as possible. The Visual Toolchest implementation is in a separate module, the XSal2 implementation, which is also in a separate module as is the M!Table implementation and the reporting engine. This approach allows the deployment of only the modules that are needed by the project.

The full C# source code is provided without charge as part of the maintenance agreement.

Using Ice Porter's unique Translation Filters technology any kind of additional processing logic can be added to the translation of the Gupta code and the generation of the new .NET code.

In addition to standard customisable filters, custom developed personalised rules can be added to normalise the UI of the application, extract documentation in a specific format, generate ad-hoc wrappers to fit in a SOA architecture, change the naming convention, and much more. There is almost no limit to what can be achieved.

Customers can also develop their own translation filters directly in C# or VB.NET.