Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

COMn and LPTn with 1-3 superscripts are not accounted for

Open Beginner friendly
  • Is something wrong?
#73 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp
Domain
tooling

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.

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

https://github.com/microsoft/vs-solutionpersistence/blob/3489af847b089e729a641a6051a02990245e8716/src/Microsoft.VisualStudio.SolutionPersistence/Model/SolutionModel.cs#L415-L418

Dominant language
C#
Stars
213
Forks
14
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vs-solutionpersistence

All issues in microsoft/vs-solutionpersistence

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.