gmStudio's code analysis and translation capabilities may be extended and modified through various rules files and scripts. In order to provide for higher control, precision, and accuracy , the specification of custom transformation is specified using various types of configuration files that extend the definitions of various language and API descriptions. This page contains many samples of different types of configuration files. The concepts and techniques for creating and using these types of files is described in other articles:
You can see this technology in action by downloading examining our Samples.
A collection of sample rules files and script is cataloged here; you may download these and experiment with them in your environment. Please Contact Us or post your questions here.
Migration Rules Files (RefactorLibrary Files) are the preferred means of mapping a COM API to its replacement in .NET. The file mig.vb7lang.xml is a special case: it may be used to modify the mapping of VB6/ASP language elements to .NET.
Custom IDFs allow you to migrate COM APIs to .NET replacements. This is a powerful and fairly intuitive technique, but it is not as maintainable as Migration Rules files.
The gmStudio samples use custom IDFs files, but this approach will be phased out in favor of using Migration Rules files. See Custom COM Replacement.
gmSL scripts may be used to implement dynamic translation rules for various COM migrations in concert with custom IDFs and RefactorLibrary files. gmSL Scripts may also be used for special purpose analysis and transformation on their own. Learn more about gmsl here: gmSLIntroduction.
Note we also offer a .NET API that has all of the power of gmSL and may be used to build custom translation engines as .NET executables.
|Table of Contents|