1% was upgraded to 2% and has a new behavior.
The Visual Basic Upgrade Companion converts VB6 library items (types and members) to .NET equivalents whenever possible. For some VB6 elements there are .NET constructs that work in a very similar way but may differ in their behavior depending on how they are used. The VBUC generates the EWI 2080 for these scenarios.
During the upgrade process, some class members can be mapped to .NET structures with minor behavior differences. If this EWI is displayed in a given project, the selected target structure will keep the functional equivalence of the resulting code but may end up having small differences in some cases that may require some manual fine tuning, such as methods that are called in a different order or text that is displayed in a different font.
- Evaluate whether the specific differences might be present on the specific code being upgraded. Sometimes these potential differences won't affect the application depending on how the original VB6 element was used.
- Apply some modification to the upgraded source code which references the conflictive elements so that the differences are resolved.
- Implement a new element in .NET that doesn’t show the conflictive behavior differences. This might be done from scratch or by taking advantage of the existing .NET elements by using extension or wrapping approaches.
- If a different element will be used instead of the one being generated by VBUC, the Custom Mappings Featurecould be used to override the preexisting conversion.
For example the VB6 SavePicture command
For example the VB6 Form_Load event
8 Proven Tips for
Planning a Successful Migration