.NET (C#) support: tracking issue

Ouverte
#137 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
csharp, typescript
Domaine
backend, testing

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
0
Forks
4
Merge moyen
18 h 41 min
PR mergées (30 j)
48

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de DiffCI/core

Toutes les issues de DiffCI/core

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.