CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - How to reproduce user issues

 This page will help you to reproduce user issues when the Technology of the application is .Net

 Perform the following steps to reproduce issue for .Net technology:

1. In order to proceed with the below steps, get the Relevant input
2. Always use a CAST AIP setup installation. For reproducing issues, flat installation is not recommended because the analysis/snapshot may fail. This can be due to files that are missing in the flat installation.
3. Import the databases mngt and local if reproducing the analysis issue else import all the three bases for snapshot issue.
4. Synchronise the databases from CAST-MS

5. Configure the analysis

   1. Open CAST-MS

   2. Get the deployment folder path.

   3. Map the source code path in order to respect the deployment defined in configuration.
   4. Go to the current Version tab and check the path of AU whether it is mapped to the same path of the deployment folder.
   5. If customer provides the complete source code then copy or map the complete source code in the mapped deploy folder and run the analysis.
   6. If customer provides only couple of files as requested by support after verifying the analysis log and understanding the issue, then create a dummy project file with the help of Visual studio or use an old project file and edit it to attach the provided source files to it and follow the DMT process in order to discover the analysis unit.Refer the official documentation
   7. Running the analysis depends on the type of issues as below:
      Crash/Fatal error: If the analysis unit causing the crash is not known then run the full analysis if it is known run only that particular analysis unit by annotating it.
      Syntax error warnings: It is not advisable to run the complete analysis while reproducing the syntax error only running couple of files giving syntax error or particular analysis unit is enough, this will save time.
      Other warnings: If the warning is related to missing assembly/missing dependency, you should never annotate the analysis unit rather study the case and check the dependency and may be annotate the analysis unit accordingly to reproduce quickly.
      Performance issue: Check in the analysis log and see which analysis unit is taking more than expected time and try to run only that analysis unit and see if the issue is getting reproduced. If the analysis log does not gives clarity on analysis unit (performance issue while loading the configuration, saving phase) then run the analysis on whole source code.
   8. Configure DLM only if the issue is related to DLM. If not required delete it from CAST-MS because while configuring the analysis you might not have the dlm.xml file, for more info please refer this page
   1. Only if the issue is related to missing links and reference pattern, configure reference pattern otherwise remove it from CAST-MS, for more info please refer this page
   2. If you don't require the settings in"Tools before analysis" and "Tools after analysis" for your reproduction then remove these configurations from Content enrichment tab in CAST-MS, for more info, please refer this page
   3. Uncheck the analysis units of other technologies if you have other technologies apart from the technology that is being analyzed but in case of missing links between inter technologies (for ex: missing links between java method and oracle table) you have to be careful while un-checking the analysis units of other technologies. This will shorten down the analysis run time, for more info, please refer this page
   4. If Architecture model is configured, the same configuration should be made, for more info, please refer this page

   5. Check all the tabs in the CAST-MS for different configuration done by customer, make sure you have the same configuration otherwise your analysis will fail at some other step and you will end up with different issue.

6. Run the analysis

Running the Analysis

Pre-requisite

The pre-requisites that need to be followed.

• .Net framework need to be installed at customer side.
• Resource package needs to be packaged properly.
• If the code is VB.Net make sure to compile the code before packaging it in DMT.

Configure the analysis

Please follow the below steps to configure the analysis:

1. Open CAST-MS and check the deployment folder path

2. Map the source code path in order to respect the deployment defined in Client Configuration
3. Go to the current Version tab and check the path of AU whether it is mapped to the same path of the deployment folder
4. Check all the tabs in the CAST-MS for different configurations done by customer, make sure you have the same configuration otherwise your analysis will fail at some other step and you will end up with different issue.
5. Check in the Content enrichment tab if Tools after analysis and Tools before analysis is configured.
6. Check if we have any architecture model configured so we need to have the same configuration at our side.

Issues because of the customer code

If customer provides the source code:

Put the complete source code in the mapped deploy folder and run the analysis.

If customer provides only couple of .cs or .vb files as requested by support, then we need to create a corresponding project by using those files provided by the customer.

How to create a project for reproduction

So in order to create a project in .net we have to use Visual Studio:

Select new project > Console Application > <Project name>

VS will create a new project and then we need to add the files and then refer those files provided by the customer in the created project file, as shown below:

We have added 2 files Test_file1.cs and Test_file2.cs in the project file and referred.

We need to package the file and run the analysis and check if the issue is getting reproduced.

If user is reluctant to provide the complete source code but they can give only couple of files which has an issue then as explained in the page above you need to use visual studio to create a project and join the files provided by customer followed by packaging, delivering, accepting the package and running the analysis.