microsoft / microsoft/vs-solutionpersistence
Add support for Solution Filters (.slnf)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 213
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Currently the .NET SDK, DevKit, and other tools that want to interact with solutions correctly have to manually implement for Solution Filter files.
- .NET SDK (via dotnet test):
- there are other places where we need to add support aside from this
- ionide/proj-info (F# tooling/VSCode)
- DevKit
- MSBuild
And surely more! This is a common tooling scenario that would benefit from a centralized implementation - in addition many of these existing parsers parse the solution in a very inefficient way: they load the entire solution and then apply the mask from the filter to the loaded solution. In an ideal world, the filter could be applied during solution parsing to limit the total amount of work done.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked MSBuild SolutionFile.cs implementation, the ionide/proj-info InspectSln.fs code, and the referenced .NET SDK changes to compare existing .slnf handling. Define the shared support and its scope across the SDK, DevKit, MSBuild, and other consumers; done should include coverage for solution filters without requiring each tool to implement its own parser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100