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?

Upgrade Options

In the following section, you will find the Upgrade Options available in the VBUC. So that you can define how the VBUC will generate the .NET code.

PreviousGenerated CodeNextData Access

Last updated 1 year ago

Was this helpful?

The upgrade options are divided into subsections, where each section refers to different types of components or categories of options supported by the VBUC:

  • : This section determines the way in which the Data Access components will be upgraded. There are options for ADODB, DAO, RDO, SQLDMO, or Oracle.

  • : Since grid components are usually the most complex third party components in a VB6 application, the VBUC has a section with options for the most commonly used ones.

  • : This section has options on how to upgrade the components that came built-in with Visual Basic 6.0; these are widely used in most VB6 applications.

  • : The controls created by this company (now called Infragistics) were widely used when VB6 was very popular. That’s why the VBUC has support for these controls, and this section defines how these controls are upgraded.

  • : With the time Mobilize has added support for other controls that are widely used by VB6 developers. These are defined in this section.

  • : This is probably the most important section in the upgrade options, and it defines different alternatives for the overall code migration, as opposed to the previous sections, that defined how to upgrade specific controls.

  • : This section has options that define different alternatives for code migration to C#, taking advantage of some features of the language.

Data Access
Grids
Microsoft
Sheridan
Others
Code Conversion
C# Features