NuGet/Home

Failed to restore NuGets from local source with trailing backslash

Open

#7,495 opened on Nov 9, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)HTML (292 forks)batch import
Area:SettingsPlatform:XplatPriority:3Type:Bughelp wanted

Repository metrics

Stars
 (1,459 stars)
PR merge metrics
 (Avg merge 464d 23h) (1 merged PR in 30d)

Description

Details about Problem

NuGet product used: NuGet.Configuration assemblies

NuGet version (4.8.0):

OS version: macOS 10.13.6

Worked before? If so, with which NuGet version: N/A

Detailed repro steps so we can see the same problem

Originally filed on Developer Community against Visual Studio for Mac.

  1. Have a NuGet.Config file that uses a backslash for a local package source.
  2. With a custom NuGet package in the package source that is defined with a backslash and a project that uses it.
  3. Get the package source information.
  4. Package source information contains a backslash.

Sample test project - https://developercommunity.visualstudio.com/content/problem/374264/failed-to-restore-nugets-from-local-source-with-tr.html

Not sure if this is would be considered a bug in NuGet. NuGet could fix up Windows path separators so things work on the Mac.

Sample Project

https://github.com/mrward/TestNuGetPackageSourceBackslashMac

Contributor guide

Research direction
Investigate where package sources are normalized and ensure trailing backslashes are replaced with forward slashes on all platforms.
Tech stack
csharp
Domain
tooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#NuGet
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60