This page talks about the prerequisites and checklist to be followed before doing the .NET analysis and also to troubleshoot any crashes while performing .net analysis.

Please select the section you are interested in from the list below.

.NET Analyzer Pre-requisite

Assembly reference and Project reference

In the application if the dependencies between projects has assemblies, then we need to look in the application. If we have the corresponding application extension (dll) in the defined folder of the project file if it is not present then we need to ask for the dll from the customer/application team and then do the packaging again after getting the dll, packaging which can be done as described below:

• Put the dll in the path mentioned in the project file.
• Put all the dlls in one folder and add that folder as a .net dll package.

If the dependencies between the projects has another project then we need to look in the application for the presence of that project file which should ideally be present.

Packaging of the .NET assemblies

The .net assemblies need to be packaged along with the source code before performing the .net analysis.

The package should be done as follows:

1. Open DMT.
2. Add new package
3. Select Automated extraction of required .net assemblies
   
4. Defining a package on C:\Windows\assembly does not extract the system assemblies. Use the below instructions instead.
   1. Choose C:\Windows\Microsoft.NET\Framework\v4.0.30319. Choosing between 32 & 64 bits is mostly a non issue. What matters is the interface, and the interface is the same in both cases. But it is important to choose a folder where you will have only one version of system libraries. If you don't, then for some projects a version might be selected, for other projects, another version, which may lead to ambiguities later.
      1. So, if you know none of the project requires a version more recent than xxx, just select C:\Windows\Microsoft.NET\Framework\v"xxx"
      2. If you don't know (or don't care), just select: C:\Windows\Microsoft.NET\Framework\v"latest available" Which will most of the time be: C:\Windows\Microsoft.NET\Framework\v4.0.30319
5. Package it

6. Check the required dll of other version need to be remediated, follow the below page which also explains how to remediate the alerts: Delivery Manager Tool - Information - Project Remediation - Remediate packaging alerts

Find an example below which explains how to remediate if you have missing assemblies, or if you have missing source files.

In the below screen shot we have 18 alerts related to missing assemblies and source files.

We have the missing assemblies mentioned below under the package content

Since the missing assemblies if of .Net framework version 4, so we need to package the .Net assmeblies of framework 4.

In DMT we have to select the automated extraction of required .Net assemblies.

After packaging we can see that in the .NET assemblies package, in the package configuration tab, there is the list of all the alerts detected, and in the package content tab the list of assemblies that found to remediate these alerts.

Then, after packaging we see that there are no more alerts related to missing assemblies in the DMT.

Now, in the below screen shot you could see there is a third party assembly which is missing.

We need to create another package and provide the path of the third party assembly.

After packaging the third party assembly the package is fine with no more DMT alerts, please find the screen shot below.

Following is the list of the main problems that can occur during a .NET analysis using the .Net analyzer. There are several types of problems: related to not following the prerequisites of the analysis, related to memory consumption or related to the code analysis.

C#.Net

Analysis Issues

In some cases, it is possible to encounter issues related to the analysis prerequisites. In the table below you will find the main messages that may be displayed by the Analyzer,. In most cases the issue can be resolved by applying the suggestion in the column Resolution.

We need to follow the prerequisites properly to avoid the errors.

Code Analysis

During the analysis, issues can appear related to the code. In the table below you will find the main messages that may be displayed by the analyzer:

In other case get the source code from customer and reproduce the issue, report to R&D. This page provides the guidelines on reproducing the issue.

Memory Issues 

During the analysis, some issues related to memory consumption can occur.

To confirm the memory issue we need to activate the AMT profiling and run the analysis, if CAST rest bytes in more than 1.8GB then it is a memory issue and then we need to follow the below troubleshooting page:

CMS Snapshot Analysis - Run Analyzer - Fatal Error - Analyzer is running out of memory - This may occur under disk full condition

Shown below are the main error messages that may be displayed by the analyzer:

VB .Net

Analysis Issues

Code Analysis

For code related issue we need to follow the same as above in the C#.NET

Memory Issues

For memory issue we need to follow the same as above in the C#.NET