This page handles the issue of missing objects after analyzing DOTNet applications using Dotnet extension.
Perform the below actions
If you have *.xproj files, these are not current supported by the dotnet analyzer. You can potentially convert them to *.csproj files which can be analyzed. This page may possibly help with this conversion: https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-migrate
Check if the source files for the missing objects are included in the project file
Open the project file in a text editor. Search for lines containing 'Compile Include' directives:
<ItemGroup> <Compile Include="Test.cs" /> <Compile Include="Test1.cs" /> <Compile Include="Program.cs" /> <Compile Include="Properties\AssemblyInfo.cs" /> </ItemGroup>
If you find a line as <Compile Include="<file_name>" /> file under examination, then the file should be analyzed and objects should be created. In this case, report your problem to CAST Technical Support with the below relevant input.
If you do not find a line as <Compile Include="<file_name>" /> under examination, then the project file is .NET core file. The .NET core file does not have class files referred to in the project file, see this page for more information. CMS Snapshot Analysis - Run Analyzer - DOTNet - Information - DOTNet core analysis. So if the source file for the missing object is present in the deploy folder and still you do not have object present in knowledge base report your problem to CAST Technical Support with the below CMS Snapshot Analysis - Run Analyzer - Missing objects - Dotnet with extension - Dotnet Analyzer#Relevant input
- If you have missing objects coming from external packages then check if the packages are present in the deploy folder. If not then generally you would have this message "No resource found for package <Package_name>. Package reference ignored in project <Project_name>". For this issue follow this page: CMS Snapshot Analysis - Run Analyzer - Warnings - DOTNet with extension - DotNet Analyzer - No resource found for package
If this does not solve the issue, report your problem to CAST Technical Support with the below CMS Snapshot Analysis - Run Analyzer - Missing objects - Dotnet with extension - Dotnet Analyzer#Relevant input
- Sherlock export with the following options: Export Logs, Export Configuration files, Export CAST Bases (Management Base and Knowledge Base), source code
- In some cases, the IN tables are also needed to investigate the missing object issue. Support will provide specific instructions to execute the following process when this is needed:
- Activate the IN Tables
- Run the Analysis.
- Take Sherlock with the above-mentioned options
- Deactivate the IN Tables