Starting from CAST AIP 8.3.23, CAST Architecture Checker will no longer be installed as part of the CAST AIP setup, whether installing CAST AIP from scratch or on a server where a previous release of CAST AIP exists. CAST Architecture Checker has evolved into a standalone component where all feature requests and bug fixes are now managed. This standalone component can be downloaded from CAST Extend (https://extendng.castsoftware.com/#/search-results?q=archichecker).
Up-to-date documentation can be found here: CAST Architecture Checker.
This section provides a detailed description of the contents of the Main window within the CAST Architecture Checker. The Main window contains various tabs, each is explained below:
The messages in the Log tab are also recorded in a log file on disk:
- the file will be named "AC-<date>-<time>.log.txt", where <date> is of the form "YYYYMMDD", and <time> of the form "HHMMSS"
- the file will by default be located in %ALLUSERSPROFILE%/CAST/CAST/Logs/ArchiChecker, or in a folder named ArchiChecker in the location specified by the CAST_LOG_ROOT_PATH if that variable has been defined and activated in the CastGlobalSettings.ini file.
The following headings are displayed in the Log tab:
|Record type||Displays the type of message:|
Describes the message.
You can also use the Filter icon to sort and filter the messages according to their content:
Only messages that match the chosen criteria will be displayed.
|Date||Date and time the message was generated.|
You can also use the options to filter and clear the messages:
|Show all||This option will list all messages, regardless of their type.|
|Show errors only||This option will list only Errors and Exceptions|
|Show reports only||This option will only list Reports.|
|Clear log||Use this option to clear the list of messages.|
|This colour highlights the link between the two objects that are violating the currently selected dependency (i.e. between two specific layers) in your model.|
|This colour highlights any other links in the current source code that are violating the currently selected dependency (i.e. between two specific layers) in your model.|
|This colour highlights any other links in the current source code that are violating a different dependency (i.e. between two specific layers) in your model.|