tech-stack-dotnet

Tech Stack: .NET

Overview

This tech stack skill provides .NET/C#-specific context for the generic workflow skills (spec-driven-development, incremental-implementation, test-driven-development) and for review agents. It is loaded when .claude/tech-stack contains dotnet.

When To Use

Loaded automatically by commands and skills when the active tech stack is dotnet. Not invoked directly.

Build & Test Commands

• Compile: dotnet build
• Test (batch): dotnet test or dotnet test --filter <project>
• Test (full): dotnet test
• Test (list-only): enumerates discovered tests without executing them — the F7/command-verification list variant used to verify dotnet test is runnable without paying for a full suite run. Conditional on the solution format:
  • .sln: dotnet test <sln> --list-tests
  • .slnx (or global.json sets "test": {"runner": "Microsoft.Testing.Platform"}): dotnet test --solution <slnx> --list-tests — a bare dotnet test <slnx> --list-tests fails with "Specifying a solution for 'dotnet test' should be via '--solution'" under Microsoft.Testing.Platform.
• Format: dotnet format --verbosity quiet (project-wide). Edited-file formatting is wired via hooks/format-on-edit.sh, which queues paths at PostToolUse and formats them at Stop — both halves must be wired or nothing is formatted. --include takes paths relative to the workspace directory, so the flush pass groups files by their nearest .csproj and runs from that directory; an absolute --include silently matches nothing and still exits 0. Do NOT reference $CLAUDE_FILE — it is not a Claude Code env var; hook input arrives via stdin.

File Extensions & Markers

How setup-bootstrap detects this stack in a repository:

Marker	Confidence
*.sln or *.slnx	High
*.csproj	High
global.json	Medium
Directory.Build.props	Medium

Detection command:

find . \( -name "*.sln" -o -name "*.slnx" -o -name "*.csproj" \) -not -path "*/bin/*" -not -path "*/obj/*" 2>/dev/null | head -5