Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Gather VB6/COM codebase:
    1. VB6 source code and resource files of type: *.vbp, *.bas, *.cls, *.frm, *.frx, *.ctl, *.ctx, *.dsr, *.dsx, *.res (as applicable). 
      These code files must be organized into directories consistent with your standard VB6 build environment. 
      If possible include only the VB6 code files that you want included in the assessment and the subsequent upgrade effort.

    2. COM binaries referenced by the *.vbp projects explicitly or through classes instantiated by name through statements like CreateObject.
      These COM binaries may include files of type: *.dll, *.ocx. *.tlb, *.exe (include any .NET assemblies if your VB6 code references them through interop).
      These files will typically have to be installed/licensed/registered properly for the VB6 to build.

    3. If available, you may share other documents such as build scripts, help files, coding standards, testing procedures, and other developer documentation.

  2. [Optional] Validate the source codebase by completing a build using the VB6 IDE.  This is not a requirement, but it is a highly recommended step.

  3. Install the gmStudio Trial on the machine with the VB6 and run the New Project Wizard. 

    This will prepare a gmStudio Project workspace folder containing supporting files (e.g. the interface description files (IDFs) for COM API descriptions) and reports.    

    We can join you in a Web Meeting to assist you with this this task if necessary.

    The gmStudio Trial may be downloaded through the downloads page after you have
    completed the Trial Request form and validated your email address.

    Note: the gmStudio Trial License limits the size of systems that may produce Translated code,
    but it does not limit the size of systems that may be processed for assessment preparation and metrics reporting.

  4. Zip the source directory and the gmStudio Project workspace folder.

    We recommend you create two zip files:
    * containing the project workspace directory files, and
    * containing the source directory files.

  5. Upload the resulting zip file(s) to a web folder we setup for you (e.g. OneDrive) or,
    you may upload your zip files to a folder (or a Virtual Machine) that you provision and we will fetch them from there.