Technical Frequently Asked Questions
What percent of my code will Yumasoft migrate automatically?
If the code is straightforward and is standards compliant without a lot of complexities, Yumasoft will migrate 99% to 100% of the code automatically. For an application that has non-standard constructs, or does nasty things with pointers and Windows API calls, Yumasoft may only migrate 90-95% of the lines automatically.
What's the relationship in size between the legacy code and the generated C# code?
Because of the number of comments generated during the migration process (for consistency and maintainability) the number of generated C# source lines will typically be one and a half to two times the number of original Dialog System lines.
Is there a limit on the size of a Dialog System module (screenset) that would prevent from being migrated to C#?
There is nothing to prevent a a Dialog System module (screenset) of any size from being migrated to C#.
Do you provide any sort of runtime library?
Yes. We have a small runtime library of supported classes that allows us to produce simpler C# code. However, we deliver the full source code of the support classes.
We would like our legacy Dialog System based application migrated to a language other then C#. Can your service create languages other than C#?
Our migration software consists of parsers and generators. A parser converts legacy code (such as Dialog System or COBOL) to an intermediate form. A generator (such as the C# generator) generates C# from the intermediate form. To generate something in a language other than C# we would need to develop a generator for that language. This is a straightforward process and we have developed generators for other languages (for example Java). Please contact us for more information.