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

To successfully deliver and analyze Visual Basic code, the following third-party software is required:

Install on workstation running the AIP Console / DMT (for delivery)

Install on workstation running AIP Node / CMS (for analysis)

Nothing required

Note that the AIP Console/CAST Delivery Manager Tool only requires the location of the VB files for extraction and packaging.
If your CAST AIP schemas are hosted on an Oracle Server RDBMS, you must ensure that a 32-bit Oracle Client (in addition to the 64-bit Oracle client that is already required) is installed and configured on the machine on which you want to use the CAST Management Studio to run the VB analysis. This requirement is due to the fact that the VB analyzer is delivered as 32-bit only (see paragraph below). You can refer to this third-party guide on installing a 32-bit and 64-bit Oracle Client on the same machine (this guide is provided "as-is" without guarantee or support from CAST).

Visual Basic analyzer and 64-bit compatibility

AIP Core is 64-bit compliant and therefore requires a 64-bit compatible machine for installation purposes, however, the Visual Basic analyzer contains components that cannot be re-factored to 64bit and therefore CAST has had to deliver these components as 32-bit modules. This has been achieved by placing the required components in the Vb6 folder located at the root of the AIP Core installation location.

Analysis of VB source code will proceed without issue, however, please note the following:

  • Because the Visual Basic analyzer is delivered as 32-bit, it is subject to the same memory limitations as any other 32-bit application.
  • If you manually modify any configuration files (such as the default AIP Core environment profiles or other .INI files), you must ensure that you modify them in the <AIP_Core_install_folder>\Vb6\configuration folder, rather than in the identical file located in the standard <AIP_Core_install_folder>\configuration folder.
  • You can still manually create Execution Units if you find that you are receiving out of memory errors when attempting to run a large Visual Basic analysis.
  • No labels