You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected result
The NuLink.TestCase.FirstPackage package linked to a local folder.
Actual result
It throws a "File does not exist" error. ParsedPath::ParsedPath(string path) in OldProjectStyle.cs uses Path.AltDirectorySeparatorChar to split paths on Windows style separarators, but it doesn't work on macOS (see this issue https://github.com/dotnet/corefx/issues/11529)
NuLink command line and output
$ nulink link -p NuLink.TestCase.FirstPackage -l "\Users\user\Projects\NuLink Test\NuLink-master\demos\NuLink.TestCase.FirstPackage\NuLink.TestCase.FirstPackage\NuLink.TestCase.FirstPackage.csproj"
Error: File does not exist: \Users\user\Projects\NuLink Test\NuLink-master\demos\NuLink.TestCase.FirstPackage\NuLink.TestCase.FirstPackage\NuLink.TestCase.FirstPackage.csproj
Steps to reproduce
Install NuLink
Run the commands to link a package on MacOS
Expected result
The NuLink.TestCase.FirstPackage package linked to a local folder.
Actual result
It throws a "File does not exist" error. ParsedPath::ParsedPath(string path) in OldProjectStyle.cs uses Path.AltDirectorySeparatorChar to split paths on Windows style separarators, but it doesn't work on macOS (see this issue https://github.com/dotnet/corefx/issues/11529)
NuLink command line and output
Error: File does not exist: \Users\user\Projects\NuLink Test\NuLink-master\demos\NuLink.TestCase.FirstPackage\NuLink.TestCase.FirstPackage\NuLink.TestCase.FirstPackage.csproj
Output of dotnet --info command
Proposed solution
Hardcoding ‘\’ as an additional separator character for the path.Split call in ParsedPath::ParsedPath(string path).
The text was updated successfully, but these errors were encountered: