microsoft / FASTER
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
txt
nuspec
in
gitattributes
filters
vcxproj
  • 19 extensions are included in analyses: cs, h, csproj, md, cc, js, txt, yml, nuspec, json, html, scss, ps1, in, gitignore, gitattributes, filters, sh, vcxproj
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (26 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (7 files).
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.

main42082 LOC (64%) 295 files
test18528 LOC (28%) 94 files
generated0 LOC (0%) 0 files
build and deployment588 LOC (<1%) 18 files
other4296 LOC (6%) 87 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
vcxproj
filters
in
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 295 files match defined criteria (42,082 lines of code, 100.0% vs. main code):
    • 232 *.cs files (30,418 lines of code)
    • 41 *.h files (9,080 lines of code)
    • 8 *.cc files (1,308 lines of code)
    • 2 *.ps1 files (422 lines of code)
    • 7 *.js files (363 lines of code)
    • 2 *.yml files (277 lines of code)
    • 1 *.vcxproj files (170 lines of code)
    • 1 *.filters files (30 lines of code)
    • 1 *.in files (14 lines of code)
  • " *.cs" is biggest, containing 72.28% of code.
  • " *.in" is smallest, containing 0.03% of code.


*.cs30418 LOC (72%) 232 files
*.h9080 LOC (21%) 41 files
*.cc1308 LOC (3%) 8 files
*.ps1422 LOC (1%) 2 files
*.js363 LOC (<1%) 7 files
*.yml277 LOC (<1%) 2 files
*.vcxproj170 LOC (<1%) 1 files
*.filters30 LOC (<1%) 1 files
*.in14 LOC (<1%) 1 files
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 ".*_test[.].*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*[.][Tt]est/.*".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 94 files match defined criteria (18,528 lines of code, 44.0% vs. main code):
    • 73 *.cs files (11,839 lines of code)
    • 5 *.h files (4,301 lines of code)
    • 14 *.cc files (2,277 lines of code)
    • 2 *.csproj files (111 lines of code)
  • " *.cs" is biggest, containing 63.9% of code.
  • " *.csproj" is smallest, containing 0.6% of code.


*.cs11839 LOC (63%) 73 files
*.h4301 LOC (23%) 5 files
*.cc2277 LOC (12%) 14 files
*.csproj111 LOC (<1%) 2 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
nuspec
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]csproj".
    • files with paths like ".*[.]nuspec".
  • 18 files match defined criteria (588 lines of code, 1.4% vs. main code):
    • 13 *.csproj files (339 lines of code)
    • 4 *.nuspec files (215 lines of code)
    • 1 *.sh files (34 lines of code)
  • " *.csproj" is biggest, containing 57.65% of code.
  • " *.sh" is smallest, containing 5.78% of code.


*.csproj339 LOC (57%) 13 files
*.nuspec215 LOC (36%) 4 files
*.sh34 LOC (5%) 1 files
Other Code
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[Ss]amples/.*".
  • 87 files match defined criteria (4,296 lines of code, 10.2% vs. main code):
    • 58 *.cs files (3,547 lines of code)
    • 18 *.csproj files (476 lines of code)
    • 7 *.md files (120 lines of code)
    • 1 *.html files (100 lines of code)
    • 1 *.js files (37 lines of code)
    • 2 *.json files (16 lines of code)
  • " *.cs" is biggest, containing 82.57% of code.
  • " *.json" is smallest, containing 0.37% of code.


*.cs3547 LOC (82%) 58 files
*.csproj476 LOC (11%) 18 files
*.md120 LOC (2%) 7 files
*.html100 LOC (2%) 1 files
*.js37 LOC (<1%) 1 files
*.json16 LOC (<1%) 2 files
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)
  • *.h files are analyzed with CppAnalyzer:
    • 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
  • *.cc files are analyzed with CppAnalyzer:
    • 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
  • *.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
  • *.js files are analyzed with JavaScriptAnalyzer:
    • 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
    • No dependency analysis
  • *.yml files are analyzed with YamlAnalyzer:
    • 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
  • *.vcxproj 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
  • *.filters 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
  • *.in files are analyzed with RustAnalyzer:
    • 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
    • No dependency analysis

2022-01-30 21:57