Change the threshold for the long path warning
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.6k
- Forks
- 276
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 1
Description
NuGet Product(s) Involved
NuGet.exe, Visual Studio Package Management UI, dotnet.exe
The Elevator Pitch
During pack, if we detect that a file path is too long for Windows/Visual Studio to Restore, we should warn the customer that what is being packed would have that problem.
Otherwise, the path issue won't be seen until a consumer tries and fails to Restore in Visual Studio.
PM UI does not currently function when restore fails.
Additional Context and Details
Inspiration from https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1488263
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 with pack behavior in NuGet.exe, the Visual Studio Package Management UI, and dotnet.exe, then compare the path-length limit used by Restore. Done means packing warns when a packaged file path would be too long for Windows or Visual Studio restore, with coverage across the named clients.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100