azure / azure-functions-vs-build-sdk

Source Code Analysis Scope

Files includes and excluded from analyses

csproj

props

targets

cmd

resx

fsx

gitattributes

txt

13 extensions are included in analyses: cs, csproj, json, props, yaml, targets, cmd, gitignore, resx, md, fsx, gitattributes, txt
4 criteria are used to exclude files from analysis:

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

100 files are included in analyses.
30 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.

2 files

Main Code

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

targets

fsx

props

cmd

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

50 files match defined criteria (2,403 LOC, 100.0% vs. main code):

36 *.cs files (1,906 LOC)
4 *.targets files (214 LOC)
1 *.fsx files (164 LOC)
6 *.props files (72 LOC)
3 *.cmd files (47 LOC)

" *.cs" is biggest, containing 79.32% of LOC.
" *.cmd" is smallest, containing 1.96% of LOC.

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]est/.*".
files with paths like ".*[.][Tt]ests/.*".
files with paths like ".*[.][Tt]ests[.].*".

23 files match defined criteria (1,240 LOC, 51.6% vs. main code):

17 *.cs files (1,120 LOC)
6 *.csproj files (120 LOC)

" *.cs" is biggest, containing 90.32% of LOC.
" *.csproj" is smallest, containing 9.68% of LOC.

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 "[/][/][ ]*".

2 files match defined criteria (116 LOC, 4.8% vs. main code). All matches are in *.cs 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 ".*[.]csproj".

files with paths like ".*[.]git[a-z]+".

files with paths like ".*/[.]gitignore".

files with paths like ".*/[.]gitattributes".

10 files match defined criteria (260 LOC, 10.8% vs. main code). All matches are in *.csproj files.

Other Code

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 ".*/[.]gitignore".

files with paths like ".*[.]txt".

15 files match defined criteria (141 LOC, 5.9% vs. main code):

13 *.json files (89 LOC)

2 *.md files (52 LOC)

" *.json" is biggest, containing 63.12% of LOC.

" *.md" is smallest, containing 36.88% 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)

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

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

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

2025-05-06 21:20