Standardized Approach beats the alternatives

We preserve the original application architecture as much as possible. We have worked on too many projects and have too many years of experience in software development and Gupta migrations to risk your business by experimenting with your code. The basic premise is that if your code worked in Team Developer, it must work in .NET.

We use many built-in and customizable refactoring techniques to transform and modernize the code and user interface without altering the original application logic and fundamental structure. Virtually no or very little risk is added using our standardized approach.

We encourage you to try and compare our solution with the alternatives. We always beat them on quality, cost, time and maintainability.

There is no limit to what you can do with applications migrated to .NET using our technology.

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

If your application looks like the image above, why not make it look like the image on the right? Once we migrate your system to .NET it is easy to use state-of-the-art reliable components to modernize your apps.

The bottom line is that technology will no longer be an impediment and you will be able to focus on features intead 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 straighforward and quite 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), analyzes all references and relationships, re-generates the application into a CodeDOM structure (XML-Like Code Document Object Model), optimizes the resulting structures, and finally feeds the final CodeDOM to code renderers that generate the final source code in 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.

Our 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 reliable.

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

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

The only third party component that we use is the FlexGrid .NET, for which we have obtained a OEM license. The database layer in the PPJ Framework is entirely based on ADO.NET and can use any ADO.NET compliant driver.

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

You also get the full C# source code for free, as part of the maintenance agreement.

Using our unique Translation Filters technology, we can add any kind of additional processing logic to the translation of the Gupta code and the generation of the new .NET code.

In addition to our standard customizable filters, we can custom develop personalized rules to normalize the UI of the application, extract documentation in a specific format, generate ad-hoc wrappers to fit in a SOA architecure, change the naming convention, and much more. There is almost no limit to what we can do.

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