JetBrains / dotnet-disassembler-plugin
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
csproj
properties
props
txt
gitattributes
resx
cmd
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main4184 LOC (72%) 60 files
test723 LOC (12%) 6 files
generated426 LOC (7%) 1 file
build and deployment185 LOC (3%) 4 files
other225 LOC (3%) 7 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cmd
props
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 60 files match defined criteria (4,184 LOC, 100.0% vs. main code):
    • 31 *.cs files (2,023 LOC)
    • 17 *.kt files (1,597 LOC)
    • 3 *.kts files (198 LOC)
    • 1 *.cmd files (178 LOC)
    • 4 *.ps1 files (124 LOC)
    • 2 *.props files (49 LOC)
    • 1 *.toml files (10 LOC)
    • 1 *.xml files (5 LOC)
  • " *.cs" is biggest, containing 48.35% of LOC.
  • " *.xml" is smallest, containing 0.12% of LOC.


*.cs2023 LOC (48%) 31 files
*.kt1597 LOC (38%) 17 files
*.kts198 LOC (4%) 3 files
*.cmd178 LOC (4%) 1 file
*.ps1124 LOC (2%) 4 files
*.props49 LOC (1%) 2 files
*.toml10 LOC (<1%) 1 file
*.xml5 LOC (<1%) 1 file
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.][Tt]ests/.*".
    • files with paths like ".*[.][Tt]ests[.].*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/[Tt]ests/.*".
  • 6 files match defined criteria (723 LOC, 17.3% vs. main code):
    • 3 *.cs files (394 LOC)
    • 1 *.kt files (296 LOC)
    • 2 *.csproj files (33 LOC)
  • " *.cs" is biggest, containing 54.5% of LOC.
  • " *.csproj" is smallest, containing 4.56% of LOC.


*.cs394 LOC (54%) 3 files
*.kt296 LOC (40%) 1 file
*.csproj33 LOC (4%) 2 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]cs" AND any line of content like "[/][/][ ]*".
  • 1 file matches defined criteria (426 LOC, 10.2% vs. main code). All matches are in *.cs files.


*.cs426 LOC (100%) 1 file
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]csproj".
    • files with paths like ".*[.]bat".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*/[.]gitattributes".
  • 4 files match defined criteria (185 LOC, 4.4% vs. main code):
    • 1 *.bat files (122 LOC)
    • 2 *.csproj files (47 LOC)
    • 1 *.gradle files (16 LOC)
  • " *.bat" is biggest, containing 65.95% of LOC.
  • " *.gradle" is smallest, containing 8.65% of LOC.


*.bat122 LOC (65%) 1 file
*.csproj47 LOC (25%) 2 files
*.gradle16 LOC (8%) 1 file
Other Code
properties
txt
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/LICENSE[.][a-z0-9]+".
    • files with paths like ".*/[.]gitignore".
  • 7 files match defined criteria (225 LOC, 5.4% vs. main code):
    • 3 *.md files (109 LOC)
    • 2 *.properties files (97 LOC)
    • 1 *.txt files (17 LOC)
    • 1 *.json files (2 LOC)
  • " *.md" is biggest, containing 48.44% of LOC.
  • " *.json" is smallest, containing 0.89% of LOC.


*.md109 LOC (48%) 3 files
*.properties97 LOC (43%) 2 files
*.txt17 LOC (7%) 1 file
*.json2 LOC (<1%) 1 file
Analyzers
Info about analyzers used for source code examinations.
  • *.cs files are analyzed with CSharpAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on namespace heuristics)
  • *.kt files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.kts files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.cmd files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.ps1 files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.props files are analyzed with XmlAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.toml files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.xml files are analyzed with XmlAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2026-01-18 17:40