microsoft / microsoft/vs-solutionpersistence
[Feature Request] Solution Import Sharing
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 213
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Add ability to import shared sections. Similar to what you can do with csproj files:
<Project Sdk="Microsoft.NET.Sdk.Web">
<Import Project="../../buildFiles/NonTest.Build.props" />
<!-- Rest of project files -->
</Project>
something like:
<Solution>
<Import Solution="../../buildFiles/baseSolution.slnx" />
<!-- Rest of Solution -->
</Solution>
where ../../buildFiles/baseSolution.slnx might be:
<Solution>
<Configurations>
<Platform Name="Any CPU" />
<Platform Name="x64" />
<Platform Name="x86" />
</Configurations>
<Folder Name="MySharedStuff">
<File Path="../.editorconfig" />
</Folder>
</Solution>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 shared serializers and models that handle traditional .sln files and new .slnx files. Determine how solution sections, configurations, folders, and files are represented, then define how an imported .slnx is resolved and merged before implementing tests for the requested examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100