microsoft / microsoft/vs-solutionpersistence
Loading and saving a .sln solution file changes its content and break target names!
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 213
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
If I load a .sln solution file and write it back, I have a lot of diffs because the Writer uses the ActualDisplayName and not the DisplayName when writing an project entry.
For example
-Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "bdehaldia", "..\bde\haldia\haldia.vcxproj", "{B1541079-334F-437C-8DF6-92C4214DC3C0}"
+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "haldia", "..\bde\haldia\haldia.vcxproj", "{B1541079-334F-437C-8DF6-92C4214DC3C0}"^M
This change does not happen when I "edit" the file through VS by adding a project etc. Also the project is displayed as bdehaldia in VS so the actual display name is actually bdehaldia.
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 tracing the Writer's handling of project entries and compare its use of ActualDisplayName with DisplayName when round-tripping a .sln file. Use the reported project entry as the reproduction case, then verify that loading and saving preserves the original target name and does not introduce unrelated content changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100