microsoft / microsoft/vs-solutionpersistence
COMn and LPTn with 1-3 superscripts are not accounted for
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 213
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Windows restrictions on COMn and LPTn include digits one through nine as well as superscripted digits one through three. Specifically, U+00B9, U+00B2, and U+00B3. See the note under "naming conventions": https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#file-and-directory-names
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 in src/Microsoft.VisualStudio.SolutionPersistence/Model/SolutionModel.cs around lines 415-418, then compare the existing COMn and LPTn handling with the linked Windows naming-conventions note. Done means the restrictions include U+00B9, U+00B2, and U+00B3 as well as digits one through nine; verify the relevant solution-persistence tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100