Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Redirect
visiblefalse
locationTECHNOS:.NET - Packaging, delivering and analyzing your source code


Panel

On this page:

Table of Contents

...

Info

Anchor
whatpackage
whatpackage
What you should package?

...

Package

Package name/type

Mandatory?

Location/path

Notes

1

Source code

(tick)

Source code root folder

Use the "Files on your file system" / SVN / TFS options in the CAST Delivery Manager Tool:

Click to enlarge

Image RemovedImage Added

2

External assemblies (third party DLL)

If required, one package per vendor.

N/A: depends on the third party

Use the "Automated extraction of .NET assemblies on your file system" option in the CAST Delivery Manager Tool:

Click to enlarge

Image RemovedImage Added

When to create this package

This package should only be created when your application uses third party assemblies.

3

.NET framework (system assemblies)

(tick)

C:\Windows\Microsoft.NET\Framework64\<use the version used by your projects>

Use the "Automated extraction of .NET assemblies on your file system" option in the CAST Delivery Manager Tool:

Click to enlarge

Image RemovedImage Added

If "C:\Windows\Microsoft.NET\Framework64\<use the version used by your projects>" is NOT available on the machine, please use the most recent framework installed on the machine instead: "C:\Windows\Microsoft.NET\Framework64\<use the most recent>".

Info
Unlike in previous releases of CAST AIP, the .NET analyzer no longer tries to extract the .NET framework assemblies during the analysis: this is why a specific package for external assemblies must be created in the CAST Delivery Manager Tool. If this package is not created and delivered, the .NET analyzer will skip all projects having a dependency to .NET assemblies, leading to incomplete analysis results.


4

Custom assemblies 

If required (typically when there are unresolved alerts)

Source code root folder (or "bin" sub-folder)

Use the "Automated extraction of .NET assemblies on your file system" option in the CAST Delivery Manager Tool:

Click to enlarge

Image RemovedImage Added

When to create this package

  • When the custom assemblies are stored in the correct location as specified in the project definition, then package #1 will retrieve them. In this case no alert will be raised by the CAST Delivery Manager Tool about missing assemblies, so in this case, there is no need to create package #4.
  • When the custom assemblies are not stored in the correct location as specified in the project definition, then package #1 will not be able to retrieve them. "Missing assemblies" alerts will be raised for package #1, so the creation of package #4 for custom assemblies located either in the source code root folder or in the "bin" sub-folder is required to clear these alerts.

...

Info

Note that an exclusion rule is active by default, which will force basic .NET web site projects to be discovered but ignored when a full .NET project exists:

Image RemovedImage Added

When using the extension ≤ 1.0.x with CAST AIP ≥ 8.3.5

...

  • create a new Version
  • create a new Packages for your .NET application source code / assemblies using the appropriate options (as explained in What you should package?)
  • define the location settings (root folder, assembly location, SVN/TFS details) of your Application source code in each package
  • Run the Package action (click to enlarge) on the entire version:

Image RemovedImage Added

  • On completion, check the following:
What to checkDescription
Package Content tab for your .NET source code package

The Package Content tab for your .NET source code package to see how the CAST Delivery Manager Tool has discovered and interpreted your .NET application. You need to pay particular attention to the following items:

  • Content State: displays the current state of the source code - if any alerts are listed, then this means that the CAST Delivery Manager Tool was not able to find all the application's source code based on configuration files such as .vpproj or .csproj. See Package Alerts tab below.
  • Projects Found: all projects found that are listed as Selected will be transformed into an Analysis Unit in the CAST Management Studio when you deliver the source code. Any that are marked as Ignored will not be automatically transformed into Analysis Units

Click to enlarge:

Image RemovedImage Added

Package Alert tab for your .NET source code packageThe Package Alert tab for your .NET source code package indicates whether any alerts have been found during the packaging process.

Alerts generally indicate that the source code package is incomplete, that there is a configuration issue or simply that there is something wrong in the source code. If these alerts are not dealt with and the Version is delivered, then there is a risk that the source code analysis executed in the CAST Management Studio will be erroneous or may not even complete.

It is up to you as the Delivery Manager to manage these alerts. Initially, you should always attempt to remediate alerts using the following methods:

  • by altering the source code package configuration (for example the root path defined in Package Configuration tab - Where is your source code? may be incorrect) and then repeating the Package action
  • by creating additional source code packages that target the missing projects, files and folders and then repeating the Package action
  • by altering your original source code and then repeating the Package action

If you still have alerts after performing the above actions, you may need to use an ignore action or remediate them manually.

Delivery Report

Use the View delivery report to check the delivery at a global level. This option will generate an XML based report that can easily be exported and lists all items in the delivery, for example:

  • Projects found
  • Alerts
  • etc.

The report will open with the default application assigned to open XML files. The report will only contain information once the Package action has been run.

Image RemovedImage Added

  • When you are happy that the extraction accurately reflects your .NET application source code, deliver the Version:

Image RemovedImage Added

Analyzing your source code

...

  • Accept and deploy the Version in the CAST Management Studio. Any projects that were discovered in the CAST Delivery Manager Tool will be transformed into Analysis Units:

Image RemovedImage Added

  • You should now check and edit (if necessary) the default automated analysis configuration settings that have been set for you during the package deployment. See .NET Analyzer - Analysis configurationPackaging, delivering and analyzing your source code.
  • When you are satisfied that you have configured your analysis correctly, we suggest that you run a test analysis at Application level before you generate a new snapshot (no results will be saved to the CAST Analysis Service):

Image RemovedImage Added

Image RemovedImage Added

  • When all issues and problems have been resolved, you can then use the Run Analysis only option to perform an analysis AND save the results in the CAST Analysis Service:

Image RemovedImage Added