Open peteraritchie opened 2 years ago
Do you mean that we should create solution folders for the intermediate folders, or that we should not create such folders?
It creates such folders now; so I'm wondering why (not entirely sure about it should not yet) it does create such folders now. i.e., there is no precedent that I can find.
We're not sure the history here so I don't have a good answer for you. Currently we're not prioritizing sln issues and improvements at the moment but will look for an opportunity in the future.
https://github.com/dotnet/sdk/blob/b054239026f9be94e55a72586d4be1637599abd2/src/Cli/dotnet/SlnFileExtensions.cs#L19
Adding an existing project to a solution can have different behavior than Visual Studio does, in that if I add an existing project to a solution in Visual Studio, a solution folder isn't automatically created if the project is in a nested folder (e.g. .\Tests\Api.Tests\Api.Tests.csproj, where the created solution folder would be "Tests").
There's currently no way to do the same thing as Visual Studio via dotnet CLI. I'm curious about the impetus for this design choice?