This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
Restoring fails when project/solution file uses spaces #866
Labels
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
AnthonySteele
pushed a commit
to AnthonySteele/NuKeeper
that referenced
this issue
May 18, 2020
NuKeeperDotNet#866 When there is a space in the file name, it needs to be quoted on the commandline As before, `ArgumentEscaper.EscapeAndConcatenate` handles this
AnthonySteele
added a commit
that referenced
this issue
May 18, 2020
* A fix for another escaping issue #866 When there is a space in the file name, it needs to be quoted on the commandline As before, `ArgumentEscaper.EscapeAndConcatenate` handles this * Changed my mind on the logging Co-authored-by: Anthony Steele <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🐛 Bug Report
Expected behavior
Spaces in file names should result in no errors during NuKeeper's
restoreoperation.Reproduction steps
Run NuKeeper in a folder that uses
My Solution.sln.Configuration
Version: 0.25.0
Platform if applicable:
This seems to fix it for me:
NuKeeper/NuKeeper.Update/Process/NuGetFileRestoreCommand.cs
Line 46 in 9ed8b8a
The text was updated successfully, but these errors were encountered: