While running .NET analysis you get the below type of warnings in your analysis log:
Line 19962: 2018-11-26 23:06:16.419355� Warning� MODULMSG ; Job execution� DOTNET.0038:Missing project dependency: S:\Sources\RDBMS\Analyzed\ig_common\Test_proj\FredCK.Test_projV2.csproj. The analysis results may be incomplete.
Line 19963: 2018-11-26 23:06:16.434370� Warning� MODULMSG ; Job execution� DOTNET.0038:Missing project dependency: S:\Sources\RDBMS\Analyzed\ig_common\Test_proj\FredCK.Test_projV2.csproj. The analysis results may be incomplete.
Line 19964: 2018-11-26 23:06:16.448383� Warning� MODULMSG ; Job execution� DOTNET.0038:Missing project dependency: S:\Sources\RDBMS\Analyzed\ig_common\Test_proj\FredCK.Test_projV2.csproj. The analysis results may be incomplete.
OR
Release | Yes/No |
|---|---|
| 1.2.x |  |
| 1.0 | |
| 1.1 | |
| 1.2 | |
RDBMS | Yes/No |
|---|---|
| CSS3 | |
| CSS2 | |
- Package the source code
- Run the analysis
Perform the below actions
Check in the analysis log to find out in which project file/source file the warnings are coming.
- If the warning is coming for the project file then it's very likely that the project file is of an old format of the .NET project (.NET 1.0 or 1.1), which some time back was not managed by the .NET analyzer. This issue is fixed in .NET analyzer 1.1.0 and above. But if you have a constraint in switching to a new analyzer you can upgrade your existing project file using VS to the latest and run the analysis.
- If the warning is coming from any cs/ascx/aspx.cs file then check if the file is physically present in the deploy folder, if the file is not present you need to check from the application team, whether we really require those files or not and work accordingly.
- If the warnings are still there even after following the 2nd or 3rd step then contact CAST Technical Support. with the Relevant Input for the reproduction of the issue
