You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This one might be a bit of a reach, but I've heard from many people that they would like traversal projects to act as solutions. Personally, it's the ease with which projects can be included. Traversal projects could make use of the familiar MSBuild properties, items, targets, and tasks known from project files.
I'm curious about people's alternative ideas, since I'm not optimistic that this can be supported. MSBuild projects are a lot more complicated, and using one as a solution would probably produce unexpected behavior.
I would still like to open the discussion for some format that's closer to MSBuild project files, so let me know if you have any ideas on how to perhaps use the MSBuild architecture to build a solution format that integrates with MSBuild. A possible format I've imagined is the following:
This is currently out of scope, but the current design attempts to separate configuration data from project data to leave the door open for multi-file formats.
I realized a couple days after opening this issue that supporting such a format seems far out of scope for at least this repo. I'm hoping that solution support can be moved entirely into MSBuild. It appears to be a very fitting tool for the job and would make expansion of the format easier, I imagine, since MSBuild already has very well-known and established syntax and more complete features like file globbing and resolving full paths.
This one might be a bit of a reach, but I've heard from many people that they would like traversal projects to act as solutions. Personally, it's the ease with which projects can be included. Traversal projects could make use of the familiar MSBuild properties, items, targets, and tasks known from project files.
I'm curious about people's alternative ideas, since I'm not optimistic that this can be supported. MSBuild projects are a lot more complicated, and using one as a solution would probably produce unexpected behavior.
I would still like to open the discussion for some format that's closer to MSBuild project files, so let me know if you have any ideas on how to perhaps use the MSBuild architecture to build a solution format that integrates with MSBuild. A possible format I've imagined is the following:
The text was updated successfully, but these errors were encountered: