aspnetcore-verification

ASP.NET Core Verification

Pre-commit and pre-deployment verification checklist for ASP.NET Core projects.

When to Activate

• Before creating a PR or merging a branch
• After completing a major refactoring
• Before deploying to staging or production
• When CI is failing and you need to diagnose

Phase 1: Build Verification

dotnet build --configuration Release 2>&1 | tail -20

Expected: Build succeeded. with 0 errors, 0 warnings (if TreatWarningsAsErrors is enabled)

Fail criteria:

• Any error CS compilation errors
• Nullable reference warnings (CS8600, CS8602, CS8603)
• Async warnings (CS4014 — fire-and-forget)

Phase 2: Roslyn Analyzers + Format Check

# Check formatting without modifying
dotnet format --verify-no-changes 2>&1

# Run static analysis
dotnet build /p:RunAnalyzersDuringBuild=true 2>&1 | grep -E "warning|error" | head -20

Expected: No changes were found for format, 0 analyzer warnings

Common issues:

• CA1062: Validate parameter not null → use ArgumentNullException.ThrowIfNull
• CA2007: ConfigureAwait(false) missing in library code
• CA1031: Catch too broad → narrow exception type

Phase 3: Tests and Coverage

dotnet test --configuration Release \
    --collect:"XPlat Code Coverage" \
    --results-directory ./TestResults \
    --verbosity minimal 2>&1 | tail -20

Expected: All tests pass, 80%+ line coverage

# Generate coverage report
reportgenerator \
    -reports:TestResults/**/coverage.cobertura.xml \
    -targetdir:TestResults/coverage-report \
    -reporttypes:TextSummary

cat TestResults/coverage-report/Summary.txt

Fail criteria:

• Any failing tests
• Line coverage below 80%
• Integration test infrastructure failures (Testcontainers not running)

Phase 4: Security Scan

# Check for vulnerable NuGet packages
dotnet list package --vulnerable --include-transitive 2>&1

# Check for outdated packages
dotnet list package --outdated 2>&1 | head -20

Expected: No critical or high severity vulnerabilities

# Scan for hardcoded secrets (manual check)
grep -rn --include="*.cs" --include="*.json" \
    -E "(password|secret|api_key|apikey)\s*=\s*[\"'][^\"']{8,}" \
    src/ | grep -vi "test\|example\|placeholder"

Phase 5: Format Verification

dotnet format --verify-no-changes --verbosity diagnostic 2>&1 | head -30

Expected: No changes were found.

If not clean, auto-fix:

dotnet format
git diff --stat

Phase 6: Git Diff Checklist

git diff --stat HEAD~1
git diff HEAD~1 -- '*.cs' | head -100

Manual checklist:

• No Console.WriteLine in non-test code (use ILogger<T>)
• No .Result or .Wait() on async calls
• No hardcoded connection strings or secrets
• All new public methods have XML doc comments (if project requires)
• No commented-out code blocks
• CancellationToken passed to all async calls

Diagnostic Commands

# Find async anti-patterns
grep -rn --include="*.cs" "\.Result\b\|\.Wait()" src/

# Find Console.Write in production code
grep -rn --include="*.cs" "Console\." src/ | grep -v test

# Find swallowed exceptions
grep -rn --include="*.cs" -A2 "catch.*Exception" src/ | grep -B1 "^--\|{ }$\|{ }\|^\s*}\s*$"

# Check for missing CancellationToken
grep -rn --include="*.cs" "async Task" src/ | grep -v "CancellationToken"

VERIFICATION REPORT

After running all phases, produce this report:

=== VERIFICATION REPORT ===
Date: [timestamp]
Branch: [branch name]

Phase 1 - Build:        ✅ PASS / ❌ FAIL
Phase 2 - Analyzers:    ✅ PASS / ❌ FAIL
Phase 3 - Tests:        ✅ PASS (N tests) / ❌ FAIL (N failures)
Phase 3 - Coverage:     ✅ PASS (XX%) / ❌ FAIL (XX% < 80%)
Phase 4 - Security:     ✅ PASS / ⚠️ WARNING (N issues) / ❌ FAIL
Phase 5 - Format:       ✅ PASS / ❌ FAIL
Phase 6 - Manual:       ✅ PASS / ⚠️ NEEDS REVIEW

Status: ✅ READY FOR PR / ❌ NOT READY

Issues to resolve:
- [list blocking issues]

Warnings (non-blocking):
- [list warnings]
===========================

READY: All phases pass, no blockers NOT READY: Any phase fails with ❌