The Visual Basic Technology editor contains various tabs. Each is explained below.
|Compare references by filename||If you select this option, the analyzer will compare ActiveX references in the .VBP file using the filename only. If the option is left blank, references are compared using the full path instead.|
|Default Handling||During the analysis, when this option is selected, the analyzer will take into account predefined constants and any #Const directives contained in the project.|
Custom Environment Profiles - only visible at Application and Analysis Unit level
This option enables you to select VB based Environment Profiles that you have created yourself (as oppose to the Environment Profiles that are pre-defined by CAST).
Environment Profiles are a set of predefined configuration settings that can be included in an analysis. An Environment Profile can be particularly useful where you have several applications that rely on the same specific settings. By creating an Environment Profile that defines these settings, you then simply include the Environment Profile in the analysis. When the analysis is run, the settings in the Environment Profile are taken into account.
For VB technologies, you can define:
Add a custom Environment Profile
To add a custom Environment Profile:
A dialog box will be displayed listing all existing custom Environment Profiles that have been created:
Select the Environment Profile you require and click OK. The profile will then appear in the list.
|Manage Environment Profiles|| The Environment Profile Manager will be displayed, enabling you to create your custom Environment Profile: |
See Using the Environment Profile Manager for more information about how to create new custom Environment Profiles.
Remove a custom Environment Profile
To remove a profile that you do not want to include in analysis:
You can remove multiple items by selecting the items in the list and then clicking the Remove button.
Process Settings - Inference Engine
|Use Inference Engine||Use this option to activate the Inference Engine during the analysis. Run time type information will be computed in order to simulate program behaviour during execution of the analyzer and thus identify additional links that would not otherwise be "discovered" using standard analysis techniques. This technology detects a reference to an object wherever its name is mentioned, regardless of the context in which this reference occurs.|
|Maximum Size for Query||When the Inference Engine is active, this value limits the number of strings that will be found during the search of each object value. |
Note that limiting the number of strings can lead to incomplete results, however, performance is improved.
Process Settings - Execution
|Execution Unit max size (MB) - only visible at Technology level.||See Working with Execution Units for more information.|
Please see the Dependencies tab for more information about this.
Please see the Reference Pattern tab for more information about this.
VB Reference Guide | Web Services (J2EE) Reference Guide