One of the most important considerations when upgrading to .NET is the final product precision and how it can be improved.
VBUC-generated source code can be fine-tuned to meet specific customer standards or policies about 3rd party library support, coding patterns or other coding standards.
There are two approaches to customize and extend the tool:
- User Extensibility and Customization: The Visual Basic Upgrade Companion features a simple yet powerful user definable extensibility approach called “Custom Maps”. The editor allows the end users to define transformation rules to convert VB6 keywords and/or third party library references to a particular .NET construction. The User Extensibility and Customization can be exploited to transform as many third party libraries or VB6 keyword usages as the users want. The overall precision and library coverage can be greatly improved by using this extensibility and customization approach.
- Proprietary Extensibility and Customization: The proprietary extensibility is performed by Mobilize.Net migration architects at the request of customers. This is the most powerful approach since it allows highly detailed transformations in the resulting source code. Since this extensibility approach is performed by our personnel, the possibilities are infinite; from adding the required transformations to upgrade a particular non-supported legacy control to its .NET counterpart with specific member handling, or to define special handling techniques for complex language patterns to be converted into optimized .NET constructions and so forth.
Read our case studies to see examples on Proprietary Extensibility and Customization.