.NET (C#) support: tracking issue

Abierto
#137 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp, typescript
Área
backend, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
4
Merge medio
18 h 41 min
PR fusionados (30 d)
48

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DiffCI/core

Todos los issues de DiffCI/core

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.