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?

Knowledge Base

PreviousAssessment Report IssueNextFAQ

Last updated 4 years ago

Was this helpful?

This section contains specific technical articles and other resources aimed towards providing a smoother experience while performing a VB to .NET migration with the Visual Basic Upgrade Companion.

Content Overview

  • :

    When upgrading a project from VB to .NET, there might be some items that are not fully converted by the VBUC, requiring some manual adjustments in order to compile and run the generated code and to achieve functional equivalence. The VBUC helps with this process by inserting different information messages (hereafter referred to as EWIs) into the migrated source code as comments. The purpose of these pages is to provide detailed information about these EWIs, along with recommendations on how to solve them.

  • :

    an exhaustive compilation of the most common technical inquiries about the Visual Basic Upgrade Companion and VB to .NET migrations in general.

  • :

    Technical documents that display tips and tricks to get the most out of Mobilize’s VB to .NET migration product and solve complex issues during the entire conversion process.

VBUC Errors, Warnings, and Issues
Frequently Asked Questions
How-To articles