Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »


Suppose you are interested in upgrading-to-.NET a number of VB6 projects, as listed in the example below:


In this example, the Migration Set contains 7 VB6 projects (.vbp), all located in the following source directory tree:

[WorkDir]\src, where [WorkDir] is D:\gmSamples\newsamples\FMstocks

Interface Description Files (IDFs)

The purpose of this exercise is to produce correct Interface Description Files (IDFs) for all the externals (libraries and components of .dll, *.ocx, *.tlb, or *.olb extension, for example) referenced by a group of well-formed VB6 projects (.vbp), as listed above for example.


It is assumed that all externals referenced by these projects are properly registered (and licensed, for third-party proprietary components) on the machine where the projects (VBPs) build correctly.
The outputs of this exercise are the IDFs (*.xml files) listed in Step 8.

Step 1. Start the gmStudio Wizard

In gmStudio, select [File][Upgrade Project Wizard …] and press [Next] when ready

Step 2. Specify Source Input Parameters

In the Form below

  1. Select the folder containing the VB projects (VB6 or ASP) you want to translate to .NET
  2. Press [Scan and Display] to get a list of projects
  3. Select the projects you want to remove from translation, if any, and press [Remove Selected]

Press [Next] when ready to move on with the selected list of projects (seven (7) in this case)

Step 3. Specify Target Output Parameters

In the Form below

  1. Enter a "Project Name" for your Translation Project
  2. Select a target "Language" (C# or VB.NET) for the translation
  3. Select the "Target IDE" (the version of Visual Studio .NET installed on your machine)
  4. Select a "COM Strategy" ("Stub Framework" by default)
  5. Select a "Project Folder" where the results (outputs) of the translation will be written
  6. Take all other default selections for "Batch Processing Options"
  7. Press [Next] when ready to move on with the actual translation

In this example, all translation outputsgenerated by gmStudio will be written in the following output directory tree:

[WorkDir]\proj, where [WorkDir] is D:\gmSamples\newsamples\FMstocks

Step 4. View Upgrade Process

The Form below shows the various translation steps as they are being completed.

  1. Press [Next] to move on to reviewing the results of the translation process.

    Step 5. Continue

    In the Form below, press the [No, thank you … Next] button, to move on.

    Step 6. Review Metrics Summary

    In the Form below, press the [Finish] button, to move on.

    Step 7. Review Results

    The Form below shows the Main Screen of the FMSLib Upgrade Project that was set up by the previous Steps (Steps 1 – 6), including the Interface Description Files ("IDFs") that were generated from all the externals (libraries or components) referenced by all the VB6 projects in this Upgrade Project.

    From the Title Menu, select [View][Interface Description Files] to move to the next step.

    Step 8. Review Generated Interface Description Files (IDFs)

    The snapshot below shows a listing of the IDFs (*.xml text files), as generated by gmStudio for all the externals referenced in this Upgrade Project. These are contained in following directory:

    [WorkDir]\proj\idf\FromIdl, where [WorkDir] is D:\gmSamples\newsamples\FMstocks

    Step 9. Archive IDFs for Distribution

    In File Explorer, select the [WorkDir]\proj\idf\FromIdl folder and right-click [Send to][Compressed (zipped) folder] in order to compress all of the IDFs into a zip file,, as shown below.

    At this point, these IDFs will be ready to "ship" for use in gmStudio – on a machine that may not have the corresponding externals properly registered (or licensed in the case of licensed third-party components).

  • No labels