There are several types of issues we want to identify and report to the users:
|Design Error||Design-time properties that can’t be migrated (eg: Form1.LinkTopic.) For these items, we add an entry to the migration log, one entry per property per object. We only add an entry if the value of the property is different than the default value. For example, if Form1.LinkTopic has a value of Form1 (the default,) then no entry is created. The property is not carried forward in the code.|
Code that will cause a compile error in .NET (eg: Form1.LinkTopic = “Foo”.) For these items, we copy the original code forward, add an entry to the migration log, and insert an UPGRADE_ISSUE: comment into the code on the line before the error.
Code which needs some user intervention. For these, insert an UPGRADE_TODO: comment in the code and add an entry to the migration log.
Code that has been significantly altered, or objects that have some behavior differences with their VB6 equivalents. For these items, insert an UPGRADE_NOTE: comment into the code on the line before the change, but do not add an entry to the log file.
User canceled, out of memory, etc. These create one entry in the migration log.
Global issues (eg: Lack of deterministic lifetime.) These create one entry in the migration log.
The following are some of the most common issues generated by our Visual Basic Upgrade Companion.