Installation
This page describes the gmStudio installation package and the requirements for running gmStudio.
Table of Contents minLevel 3
Hardware Requirements
One of the first steps in any migration effort is to provision a development machine that will be used to perform migration work. This is typically one of the workstations already being used in maintaining and building the source codebase.
...
The methodology produces many outputs: logs, model files, reports, .NET codes and assemblies. Plan for about one gigabyte of disk space for these files.
Software Requirements
The system has been tested on:
- Windows XP SP3, Windows Server 2003, Windows 7
- .NET 2.0 or higher Framework SDK
- VB6 to validate/build VB6 codes
- IIS to validate ASP sites
- VB Migration Assessment tool (optional)
- Visual Studio 2005, 2008, or 2010 (or other application associated with csproj/vbproj files). This guide assumes you have associated a version of Visual Studio with csproj/vbproj files.
- Your choice of a programmer's text editor; we use Notepad++ (default = notepad.exe, not recommended) Note: when running in Visual Studio, the VS editor will be used.
- Your choice of a file and directory comparison tool; we use BeyondCompare from Scooter Software.
Your choice of tab-delimited file viewer (launched by associated application); we use Excel.
Installed Files
gmStudio Product
gmStudio is installed by a Windows Installer setup file (gmStudioSetup.msi).
...
[AppDataFolder]
|
\---GreatMigrations
|
+---workspace: will contain your migration workspaces and migration project files
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.
...
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.
...