Versions Compared

Version Old Version 3 New Version 4
Changes made by

Mark Juras

Mark Juras

Saved on

Key

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

...

   [AppDataFolder]
      |
      \---GreatMigrations
          |
          +---migrations: will contain your migration project files (*.gmproj)
          |
          +---workspace: will contain your migration workspaces
          |
          \---support: translation config files
              |
              +---GenInterop: working directory for creating Interop assemblies
              +---Metalang: language config files
              \---settings: gmStudio script templatestemplates 

 

 Verifying Verifying the Install

The process described below does a direct, default migration of a small project (comprised of two VBPs); it can also be used to verify your installation.

...

   -- VBPs referencing up to 50K lines of code (LOC) should finish in under 205 seconds.
   -- VBPs referencing   50-100K lines should finish in under two30 minutesseconds.
   -- VBPs referencing  100-200K lines should finish in under fiveone  minutes.
   -- VBPs referencing  200-400K lines should finish in under twentytwo minutes.
   -- VBPs referencing  400-600K lines should finish in under fortysix minutes.

Note that translation runtime is not directly proportional to the number of lines. The runtime is sensitive to the total number of symbols and atomic operations defined in the codebase being translated. This includes all identifiers declared by the VB6 code as well as all the identifiers declared in referenced COM components as well as all operations on those symbols and any literal quantities in the code. Larger codes tend to depend on more external libraries so they take proportionately longer.

Outputs

The .NET project files will be in the default deployment folder

...

      [INSTALLDIR]\samples\workspace\[name]\log

where:

      [name] is the name you entered for your migration project.

      [project] is the name of the VBP file selected above.

      [lang] is "csh" for C# or "vbn" for VB.NET depending on the task settings

Where can you go from here?

...

  • You can inspect the generated code (written in the files of the deployment folder) by selecting a migration task and right clicking [Open .NET Project Folder] from the context menu. 
     
  • You can try to compile the generated code by clicking the [DevEnv] button on the Toolbar (and thus opening the .NET project in Visual Studio). 
     
  • You can use gmStudio to browse, analyze, and summarize the various migration logs. 
     
  • You can read the remaining sections of this guide, experiment and explore. 
     
  • You can contact us for a assistance or a guided tour.