microsoft / vs-editor-api
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
resx
props
targets
vsixmanifest
txt
proj
gitattributes
editorconfig
pub
  • 17 extensions are included in analyses: cs, csproj, resx, props, targets, md, gitignore, vsixmanifest, txt, sh, xml, json, proj, gitattributes, editorconfig, yml, pub
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 files).
    • exclude files with path like ".*[.]resx" (The resx resource files) (12 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) (1 file).
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.

main78491 LOC (95%) 1408 files
test0 LOC (0%) 0 files
generated1091 LOC (1%) 12 files
build and deployment1201 LOC (1%) 42 files
other1178 LOC (1%) 28 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
targets
props
proj
pub
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 1408 files match defined criteria (78,491 lines of code, 100.0% vs. main code):
    • 1,395 *.cs files (78,109 lines of code)
    • 5 *.targets files (211 lines of code)
    • 6 *.props files (137 lines of code)
    • 1 *.proj files (32 lines of code)
    • 1 *.pub files (2 lines of code)
  • " *.cs" is biggest, containing 99.51% of code.
  • " *.pub" is smallest, containing 0% of code.


*.cs78109 LOC (99%) 1395 files
*.targets211 LOC (<1%) 5 files
*.props137 LOC (<1%) 6 files
*.proj32 LOC (<1%) 1 files
*.pub2 LOC (<1%) 1 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 "[/][/][ ]*".
  • 12 files match defined criteria (1,091 lines of code, 1.4% vs. main code). All matches are in *.cs files.


*.cs1091 LOC (100%) 12 files
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 ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]csproj".
    • files with paths like ".*[.]sh".
  • 42 files match defined criteria (1,201 lines of code, 1.5% vs. main code):
    • 40 *.csproj files (1,124 lines of code)
    • 2 *.sh files (77 lines of code)
  • " *.csproj" is biggest, containing 93.59% of code.
  • " *.sh" is smallest, containing 6.41% of code.


*.csproj1124 LOC (93%) 40 files
*.sh77 LOC (6%) 2 files
Other Code
csproj
vsixmanifest
targets
props
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]editorconfig".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[Ss]amples/.*".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 28 files match defined criteria (1,178 lines of code, 1.5% vs. main code):
    • 6 *.csproj files (675 lines of code)
    • 10 *.cs files (261 lines of code)
    • 5 *.md files (171 lines of code)
    • 2 *.vsixmanifest files (40 lines of code)
    • 2 *.xml files (20 lines of code)
    • 1 *.json files (7 lines of code)
    • 1 *.targets files (2 lines of code)
    • 1 *.props files (2 lines of code)
  • " *.csproj" is biggest, containing 57.3% of code.
  • " *.props" is smallest, containing 0.17% of code.


*.csproj675 LOC (57%) 6 files
*.cs261 LOC (22%) 10 files
*.md171 LOC (14%) 5 files
*.vsixmanifest40 LOC (3%) 2 files
*.xml20 LOC (1%) 2 files
*.json7 LOC (<1%) 1 files
*.targets2 LOC (<1%) 1 files
*.props2 LOC (<1%) 1 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)
  • *.targets 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
  • *.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
  • *.proj 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
  • *.pub 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


2022-01-30 14:57