.NET (C#) support: tracking issue

Aperta
#137 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp, typescript
Ambito
backend, testing

Direzione di ricerca

Read the adapter guide and use the Maven adapter at src/repo/adapters/maven.ts as the closest model; the registration point is src/repo/adapters/index.ts, and the release boundary is docs/release-boundary.md. Start with one unblocked step, such as mapping SDK-style project files or discovering test projects from a solution. Done means implementing the selected step with conservative blockers for unsupported MSBuild forms; the tracking issue also calls for replaying on a public .NET repository and publishing the report.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

adapter enhancement help wanted

DiffCI works out what a change needs from CI, starting with the tests it affects, so AI coding agents (and people) can run them before pushing. It supports JS/TS, Vue, Go, Maven, pytest and Cargo today. .NET (C#) is open for contributors and design partners.

First supported setup: a solution (.sln / .slnx) of SDK-style .csproj projects linked by <ProjectReference>, with test projects using xUnit, NUnit or MSTest, run with dotnet test. Selection happens at the project level first.

Steps (each is one PR; take any that are unblocked):

  • Map files to projects: SDK-style projects include every .cs file under their directory by default, minus nested projects and explicit <Compile Remove> entries
  • Discover test projects (<IsTestProject>, or a reference to Microsoft.NET.Test.Sdk) from the solution file
  • Select test projects by <ProjectReference> dependency, transitively
  • Generate dotnet test path/to/Tests.csproj commands for the selected test projects
  • Fall back with a reason on what the graph can't see: Directory.Build.props / Directory.Build.targets, Directory.Packages.props, global.json, NuGet.config, custom MSBuild targets or imports, conditional ItemGroups, linked files (<Compile Include="../...">), source generators
  • Register the adapter in REPOSITORY_ADAPTERS (src/repo/adapters/index.ts) and add it to the release boundary
  • Replay on one public .NET repository and publish the report

Ground rules

  • MSBuild files are code, not data. Read them statically and only trust simple, recognisable forms; anything else records a blockers entry and DiffCI runs the full suite. An empty graph must never look like "nothing affected".
  • Don't execute dotnet or MSBuild to fill gaps; the engine doesn't install or run project tooling.
  • Read the adapter guide first; the Maven adapter (src/repo/adapters/maven.ts) is the closest model (modules and declared dependencies).
  • Discuss design questions here, so every step stays consistent.

Using .NET and want to help, or have a repository we could test against? Say so below. 👍 this issue if you'd use it; reactions on the language tracking issues decide what comes after.

Lingua principale
TypeScript
Stelle
0
Fork
4
Merge medio
18h 41m
PR unite (30g)
48

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DiffCI/core

Tutte le issue di DiffCI/core

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.