VBUC Documentation | Mobilize.Net
Mobilize.NetForumsBlogDocumentation Home
  • Mobilize.Net VBUC
  • Introduction
  • Install and Licenses
  • Get Started
  • Migration Guide
  • VBUC Features
  • Mappings Grammar
  • Generated Code
  • Upgrade Options
    • Data Access
    • Grids
    • Microsoft
    • Sheridan
    • Others
    • Code Conversion
    • C# Features
  • Third-party controls
  • Best Practices
  • EWIs
    • Warnings
    • Issues
    • ToDos
    • Notes
  • Issues and Troubleshooting
    • Microsoft.VisualBasic Uses
    • Safe and Unsafe Methods Layer
    • Third Party Components
    • Migration Process
    • Classic ADO Conversion to ADO.NET
    • VB6 and .NET integer division
    • VB6 On Error Statements
    • Running a .NET Core application in a machine with no Visual Studio installed
    • Databases issues
    • Unsupported assemblies on .NET Core and .NET 5
    • Icon Extraction Issues
    • HTTPS sites are not loaded in Windows XP
    • Short-Circuit Boolean Logic in C#
    • Assessment Report Issue
  • Knowledge Base
    • FAQ
      • Does the VBUC support the Sheridan VB 6.0 controls suit?
      • How effective is the Visual Basic Upgrade Companion tool at converting an application's front end?
      • What controls does the Visual Basic Upgrade Companion tool supports?
      • How does the VBUC handle VB6 Collections?
      • Can the VBUC migrate intrinsic VB6 functions and libraries?
      • Where is the source code for the support (helper) classes used by the VBUC?
      • How does the VBUC convert ADO to ADO.NET?
      • Can the Visual Basic Upgrade Companion tool be customized?
      • What are Stubs?
    • How-To
      • App.Config and Database Access
      • Avoid reflection in Hot Paths
      • Convert ESRI ArcGIS Visual Basic 6.0 applications to .NET
      • Drag and Drop Conversion Steps
      • Inserting elements in a ListView
      • String vs StringBuilder
      • Word Automation in VB6 vs .NET
      • Configure default Factory Database provider
      • GetPrivateProfileString Windows API working in migrated code
      • Upgrade projects with shared files
  • Release Notes
Powered by GitBook
On this page

Was this helpful?

  1. Knowledge Base
  2. FAQ

How effective is the Visual Basic Upgrade Companion tool at converting an application's front end?

The Visual Basic Upgrade Companion actually does an outstanding job when upgrading the applications front end, thanks to the considerations taken like:

  1. Successful default properties extraction from the original VB6 controls

  2. Use of inherent .NET controls and constructions, which ensures the resulting graphical front-end will look as natural as possible

  3. Absence of a proprietary runtime, which elevates the code maintainability and eases the process of future additions to the existing front end

  4. Clever implementations of upgrade issues like control arrays and default properties resolution even in late-bound usages

  5. Extensibility model that allows the tool to adapt to particular code patterns and programming techniques

Also, during the conversion process, the Visual Basic Upgrade Companion will display all the conflicts and issues related to references or 3rd party libraries and other resources.

PreviousDoes the VBUC support the Sheridan VB 6.0 controls suit?NextWhat controls does the Visual Basic Upgrade Companion tool supports?

Last updated 2 years ago

Was this helpful?