...
The methodology produces many outputs: logs, model files, reports, .NET codes and assemblies. Plan for about one gigabyte of disk space for these files.
| Warning |
|---|
As of December 2023, the gmStudio product package requires a 64bit Windows OS. If you are maintaining an old 32-bit Windows machine just for VB6, you will have to install gmStudio elsewhere.
In that situation, you should plan to track down the code and COM files referenced by your VB6 application and copy them to a more contemporary machine where you will use gmStudio. Ideally, you should install the VB6 IDE and the COM packages (trial editions are fine) needed by your application on the machine with gmStudio. There should be no problem with finding and copying VB6 code files (vbp, bas, cls, frm/frx, ctl/ctx, etc.) but COM files can be more difficult. Assuming you are able find the installers or files, you may still have COM APIs that are no longer compatible with current Windows. If you cannot install a COM package, you should be able to get by with only a copy of copy of the binary files. It is usually possible to create COM Interface Description Files directly from binary files (dll, ocx, tlb, etc. ) even if the COM packages cannot be installed, but your mileage will vary. See this article and contact us if you need support with this. BTW: With a little manipulation of INI files and exclusion of a few rarely used features, it is possible to install and use the VB6 IDE (albeit in compatability mode and as administrator) on Windows 10 and Windows 11. Time will tell if VB6 will also work for Windows 12. Here is one such article with additional information on how to install VB6 on new Windows. |
Development Workstation Requirements
...