About common issues when upgrading code
In the upgrade phase, developers use the Microsoft Visual Studio's Visual Basic Upgrade Wizard to auto-translate code from the VB6 to VB .NET language. Once the Visual Basic Upgrade Wizard has completed, developers can fix compiler errors and warning messages, and modify various project level settings.
This section in the software development kit (SDK) provides specific examples ArcGIS developers face on how to overcome issues that are not auto-translated correctly when upgrading from VB6 to VB .NET. This section includes topics to assist developers in fixing compiler errors and understanding warning messages for code that is auto-translated from VB6 to VB .NET.
See Also:
Migrating from VB6 to VB.NETGeneral steps for migrating from VB6 to VB.NET
Web resources for migrating from VB6 to VB.NET
Fixing OLE_HANDLE values of Bitmap properties for commands, tools, and dockable windows
esriSystem.IUID values translate incorrectly
Loading Windows forms has different behavior
Setting default Object properties to IColor is problematic
stdole library not added to migrated project
Command and Tool Bitmap property expects hWnd to display bitmaps
Registering COM interop
Common issues when advancing code from VB6 to VB.NET