| Redirect | ||||
|---|---|---|---|---|
|
| Panel | |
|---|---|
On this page:
|
...
| Info |
|---|
You can refer to the existing official CAST AIP documentation for more information about the CAST Delivery Manager Tool packaging and delivery process - see: Delivery .NET Analyzer - Packaging, delivering and analyzing your source code. |
| Anchor | ||||
|---|---|---|---|---|
|
...
Package | Package name/type | Mandatory? | Location/path | Notes | ||
|---|---|---|---|---|---|---|
1 | Source code |
| Source code root folder | Use the "Files on your file system" / SVN / TFS options in the CAST Delivery Manager Tool: Click to enlarge
| ||
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
When to create this package This package should only be created when your application uses third party assemblies. | ||
3 | .NET framework (system assemblies) |
| 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
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>".
| ||
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
When to create this package
|
...
| 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:
|
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:
- On completion, check the following:
| What to check | Description |
|---|---|
| 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:
Click to enlarge:
|
| Package Alert tab for your .NET source code package | The 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:
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:
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.
|
- When you are happy that the extraction accurately reflects your .NET application source code, deliver the Version:
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:
- 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):
- On completion, you should check the test analysis log file and then clear up any warning or error messages that have been returned by reconfiguring the analysis - see .NET Analyzer - Analysis messagesPackaging, delivering and analyzing your source code messages for more information about log messages:
- 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:
