azure / durabletask - 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

props

gitattributes

targets

resx

txt

editorconfig

dotsettings

sfproj

16 extensions are included in analyses: cs, csproj, json, md, xml, yaml, props, gitignore, gitattributes, targets, resx, ps1, txt, editorconfig, dotsettings, sfproj
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (3 files).
exclude files with path like ".*[.]resx" (The resx resource files) (1 file).
exclude files with path like ".*/docs/.*" (Documentation) (4 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).

The source code folder contains 630 files:

586 files are included in analyses.
44 files are excluded from analyses:

Explore all 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.

364 files

140 files

6 files

76 files

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

props

targets

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

364 files match defined criteria (37,956 LOC, 100.0% vs. main code):

361 *.cs files (37,790 LOC)
2 *.props files (146 LOC)
1 *.targets files (20 LOC)

" *.cs" is biggest, containing 99.56% of LOC.
" *.targets" is smallest, containing 0.05% of LOC.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

csproj

sfproj

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]est/.*".
files with paths like ".*[.][Tt]ests/.*".
files with paths like ".*[.][Tt]ests[.].*".
files with paths like ".*/TestData/.*".
files with paths like ".*[.][Tt]est[.].*".

140 files match defined criteria (19,409 LOC, 51.1% vs. main code):

118 *.cs files (18,753 LOC)
11 *.csproj files (309 LOC)
1 *.ps1 files (199 LOC)
9 *.xml files (101 LOC)
1 *.sfproj files (47 LOC)

" *.cs" is biggest, containing 96.62% of LOC.
" *.sfproj" is smallest, containing 0.24% of LOC.

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 ".*[.]csproj".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitattributes".

6 files match defined criteria (229 LOC, 0.6% vs. main code). All matches are in *.csproj files.

Other Code

csproj

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 ".*[.]editorconfig".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[Ss]amples/.*".
files with paths like ".*[.]json".
files with paths like ".*[.]txt".

76 files match defined criteria (3,031 LOC, 8.0% vs. main code):

47 *.cs files (2,339 LOC)
14 *.json files (300 LOC)
9 *.md files (268 LOC)
6 *.csproj files (124 LOC)

" *.cs" is biggest, containing 77.17% of LOC.
" *.csproj" is smallest, containing 4.09% of LOC.

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)

*.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

*.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

2025-05-06 21:11