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 10 Next »

Hardware

Upgrading large complex systems is a CPU and memory intensive process.  You will want to provision a workstation accordingly.  A "big" developer workstation is recommended.  

System Tools

  • gmStudio.exe: a desktop/console application that facilitates performing the tool-assisted rewrite tasks and working with migration artifacts.
     
  • gmBasic.exe: a configurable VB6/ASP/COM compiler that generates .NET code and other useful information; the translation engine of gmStudio. 
     
  • Deploy.exe: a "shell interpreter" utility that deploys translation results in target folders and files. 
     

  • Migration DLLs: DLLs that modify, extend, and enhance the behavior of gmBasic to produce heavily reengineered code or specialized code analysis reports.

External Tools

  • VB6.exe: a magical language processor that converts VB6/COM code into business applications. Note: VB6 is optional; it is used for validating the VB6 code on the upgrade workstation.
     
  • MSBuild.exe: a build management system for .csproj or .vbproj projects (included with the .NET SDK) 

  • Visual Studio: the .NET development IDE.  gmStudio can integrate with several different versions of Visual Studio.
     

  • Programmer's Text Editor: your favorite text editor. We use Notepad++.  
     

  • File Comparison Tool: your favorite file/folder comparison tool. We use Scooter Software's Beyond Compare. 
     
  • Windows Shell: we use the shell to open various files (*.tab, *.log, *.vbp, *.csproj, *.vbproj, *.idl) 
     
  • User Command Scripts: for injecting custom steps into the migration process (e.g., FxCop, Nant, NUnit). If you associate a console script template with a migration unit in your Migration Project, gmStudio will open it, set processing parameters, and run it at key points during processing. This can be used for custom processing tasks (post translation, post deployment, or post build). For example, one use of this feature might be to install the translation in a test environment and run a series of automated tests after each build.

    The UserCommand script template is discussed in the Reference section.

    External Tools

    You can use the Configuration\UserDefaults dialog to set most of your settings. In some cases you may need to modify the application configuration file, gmStudio.cfg, so that gmStudio can find and run the external tools in your environment.

  • Reporting tools: the tab delimited reports generated by gmStudio are typically viewed through a spreadsheet application like MS Excel.  In many cases the reports can be quite large, including over a million records and they are loaded into a relational database such as SQL server.
  • No labels