-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Is your feature request related to a problem? Please describe.
While solutions are the traditional way to manage multi-project build and orchestration in the .NET ecosystem due to their IDE support, the Traversal MSBuild SDK is often used by large teams or power users that want more direct control of their repo-wide build experiences. These projects mimic many of the benefits of solutions, while allowing for a more natural way to express build-level dependencies, easier Target definitions, and more 'clean' alignment to traditional MSBuild semantics.
Today, Traversal projects are treated like 'normal' projects by the .NET CLI for non-MSBuild commands. Commands like test, format, reference add, and more attempt to interact just with the Traversal project instead of 'unwrapping' the project to discover its contained project graph - like they do for solutions.
Describe the solution you'd like
The dotnet CLI should natively support traversal projects in all of its commands and experiences. It should provide patterns for contributing teams to correctly consume and work with such projects. It should enable easily creating new traversal projects.
Additional context
Traversal projects are often used by large teams inside Microsoft to make common repo-management tasks easier.