This repository landscape provides tooling, libraries, and workflows designed to streamline development efforts across the SDLC, with a strong emphasis on DevSecOps practices.

The goal is to ensure a smooth, consistent, and repeatable way of working with code—across development, testing, security analysis, packaging, and deployment.

• Purpose & Scope
• Repository Landscape
  • Application & Library Repositories (.NET)
  • CI/CD & Automation
  • Infrastructure & Runtime
• Engineering Conventions
  • Repository Structure
  • Source Layout (Applications & Libraries)
  • Infrastructure as Code
• Architectural & Design Principles
• References
• Credits & Appreciation

Core libraries, frameworks, and extensions targeting modern .NET development:

• Cuemon for .NET
• Savvy I/O
• Shared Kernel API
• Unitify API
• Bootstrapper API
• Extensions for xUnit API
• Extensions for BenchmarkDotNet API
• Extensions for YamlDotNet API
• Extensions for Globalization API
• Extensions for Asp.Versioning API
• Extensions for Swashbuckle.AspNetCore API
• Extensions for Newtonsoft.Json API
• Extensions for AWS Signature Version 4 API

Composable GitHub Actions workflows intended to standardize CI/CD pipelines:

• jobs-dotnet-restore
• jobs-dotnet-build
• jobs-dotnet-test
• jobs-dotnet-pack
• jobs-nuget-push
• jobs-sonarcloud
• jobs-codecov
• jobs-codeql

Low-level, reusable GitHub Actions used by workflows:

• dotnet-restore
• dotnet-build
• dotnet-test
• dotnet-pack
• nuget-push
• codecov-scan
• codeql-scan
• sonarcloud-scan
• install-dotnet
• install-nuget
• minver-calculate
• git-checkout
• shell-globbing

• Terraform

• Status Monitor

Each repository must contain the following at its root:

• README.md
• CONTRIBUTING.md
• CODE_OF_CONDUCT.md
• LICENSE
• CHANGELOG.md

All ignore files (.gitignore, .dockerignore, etc.) must also be placed at the root.

• src/ — all production source code that is shipped, versioned, and consumed by users (libraries and applications),
• test/ — all unit, integration, and regression tests that verify correctness and behavior of production code,
• tooling/ — all internal developer tools and infrastructure used to build, run, analyze, or orchestrate the repository (e.g., benchmark runners, generators, CI helpers),
• tuning/ — all performance benchmarks and microbenchmarks (BenchmarkDotNet projects) used to measure, compare, and tune runtime characteristics; not correctness tests.

Supporting assets should be placed in dedicated root-level folders, such as:

• .github
• .nuget
• .codecov
• .docfx

Repositories containing IaC should define environment-specific folders:

• origin — local development
• development
• staging
• production

• SOLID
• DRY
• Consistency
• Generality
• Abstraction
• Modularity
• Separation of Concerns
• Measure Twice, Cut Once

• Microsoft Engineering Guidelines
• Design Patterns
• Options Pattern
• Separation of Concerns in Software Design
• Clean Code in 5 minutes
• The Boy Scout Rule
• Manifesto for Software Craftsmanship

Building and maintaining a comprehensive sidecar ecosystem for .NET requires significant effort, ongoing refactoring, and high engineering standards.

This work is made possible in part through the support of our sponsors, to whom we are sincerely grateful.

The All Products Pack has been generously provided by JetBrains in support of Cuemon for .NET, part of the Codebelt family of projects.

In particular, ReSharper plays a central role in the daily development workflow, contributing directly to code quality, safe refactoring, and long-term maintainability.

We would also like to acknowledge GitHub for providing the platform and tooling that make collaboration, issue tracking, CI/CD workflows, and open-source distribution possible.

GitHub’s infrastructure plays an essential role in enabling transparent development, community contributions, and long-term project visibility.