CAST AIP 8.3.x Documentation
Page tree
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 12 Next »

On this page:

Summary: CAST AIP 8.3.5 introduces a number of features and changes as listed below. To view the impacts of these changes on analysis results, see: Changes in results post upgrade.

Technology support changes

Please see Technology coverage changes in CAST AIP 8.3.x for more detailed discussion of this subject.

.NET - discoverers modified to take into account .NET Core/.NET Standard

When using the the .NET Analyzer ≤ 1.0.x with CAST AIP ≥ 8.3.5 and if your source code contains .NET Core 2.0 / .NET Standard 2.0 projects, then these projects will be discovered during the packaging in the CAST Delivery Manager Tool. This is due to a change in the existing .NET discoverers for the .NET Analyzer that are embedded in the CAST Delivery Manager Tool. These discoverers have been modified in CAST AIP ≥ 8.3.5 to take into account .NET Core 2.0 / .NET Standard 2.0 projects in preparation for .NET Core 2.0 /.NET Standard 2.0 analysis support in the forthcoming version 1.1.x of the .NET Analyzer.

What constitutes a .NET Core 2.0 / .NET Standard 2.0 project?

The CAST Delivery Manager Tool will discover .NET Core 2.0 / .NET Standard 2.0 projects when the .csproj or .vbproj files contains the following:

<Project sdk="">
...
</Project>


Analysis of . NET Core 2.0 / .NET Standard 2.0 projects when using the extension ≤ 1.0.xAll source code in the root folder (and any sub-folders) selected for the package will be included in the project.

Analysis of these projects/Analysis Units will be successful (i.e. no errors), however, the analysis will be incomplete:

  • There will be no links to the .NET Core 2.0 / .NET Standard 2.0 framework
  • No client server/links links
  • Frameworks are not handled
  • Some Rule may produce false negatives
See also: Changes in results post upgrade - 8.3.5

Installation and deployment

Upgrade - batch file changes

The upgrade batch files (see Automating the CAST AIP Upgrade process) has been modified as follows:

  • a new option "<discoverers_to_enable>" is available in CASTUpgrade_Schemas.txt to enable specific discoverers on existing CAST Delivery Manager Tool packages (i.e. those that are being upgraded).  In normal circumstances, no discoverer is enabled for existing CAST Delivery Manager Tool packages (to eliminate the impact to post-upgrade snapshot results), however in some circumstances, it is desirable to enable a particular discoverer. You can enable discoverers for the Web Files Discoverer and the DMT XML Scanner. See Automating the CAST AIP Upgrade process for more information.
  • a new option "INSTALL_CUSTOM_UA_LEGACY" is available in CASTUpgrade_Steps.txt. It enables you to choose whether any custom legacy language packs that are present in <CAST_ALL_USERS_PATH>\configuration\languages where <CAST_ALL_USERS_PATH> is the value defined in the CastGlobalSettings.ini file (the default value is %PROGRAMDATA%\CAST\CAST\<version>) will be installed as part of the upgrade. Set to N (default) to ignore these legacy language packs, or Y to install them as part of the upgrade process.

CAST Management Studio

GUI

Discoverers to activate option

A new option has been added to the Add version dialog box called Discoverers to activate. This option is visible when you are adding a new Version based on an existing version. It allows you to specify the discoverers you would like to enable in the existing packages that will be copied into the new Version (in normal circumstances, newly installed discoverers are not enabled by default for existing packages (only for new packages)):

You can enter either any of the following (if you enter multiple discoverers, separate them with a comma):

Note that when the "HTML5 project" option is used, the feature is specifically targeted for CAST AIP upgrades when you are generating the post-upgrade consistency snapshot and need to enable specific discoverers in existing packages to maintain consistency.

CLI

AutomateVersion

An new parameter has been added to the AutomateDelivery option, called -discoverers. This allows you to specify the discoverers you would like to enable in the existing packages that will be copied into the new Version. You can select "HTML5 project" (Web Files Discoverer) and "XML scanner" (DMT XML Scanner). See Automating CAST Management Studio tasks for more information.

Note that when the "HTML5 project" option is used, the feature is specifically targeted for CAST AIP upgrades when you are generating the post-upgrade consistency snapshot and need to enable specific discoverers in existing packages to maintain consistency.

CAST Delivery Manager Tool

GUI

First Package Date

A new field is displayed at Version level to indicate the very first time the packaging action was run on the Version. If the Version has not yet been packaged, then nothing is displayed. This field will always show the very first date/time the package action was run on the Version - even if multiple package actions have been run:

  • No labels