This project has moved. For the latest updates, please go here.

Network path fails to build


Unfortunately had to uninstall this package for this error.

This package doesn't seem to want to build when this is installed and the project is at a network path. We use network paths when developing on Macs using Parallels.

If I copy the project to a normal C:\xxxx path, the build and package works as expected.

Error The command "REM Create a NuGet package for this project and place the .nupkg file in the project's output directory.
REM If you see this in Visual Studio's Error List window, check the Output window's Build tab for the actual error.
ECHO Creating NuGet package in Post-Build event...
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '\Mac\AllFiles\FileStore\GitHub\xxxxxxxxxxx_CreateNewNuGetPackage\DoNotModify\CreateNuGetPackage.ps1' -ProjectFilePath '\Mac\AllFiles\FileStore\GitHub\xxxxxxxxxxx\yyyyyyy.csproj' -OutputDirectory '\Mac\AllFiles\FileStore\GitHub\xxxxxxxxxxx\yyyyyyy\bin\Debug\' -BuildConfiguration 'Debug' -BuildPlatform 'AnyCPU'"" exited with code 1.

The build output is:

VERBOSE: Using NuGet Version:
1> VERBOSE: Performing any required New-NuGetPackage script cleanup...
1> An error occurred while running New-NuGetPackage script:
1> Exception calling "GetDirectoryName" with "1" argument(s): "The path is not of a legal form."
1> Get-ProjectsAssociatedNuSpecFilePath : Exception calling "GetDirectoryName" with "1" argument(s): "The path is not of
1> a legal form."
1> At \Mac\AllFiles\FileStore\GitHub\xxxxxxxxxxx\yyyyyyy_Create
1> NewNuGetPackage\DoNotModify\New-NuGetPackage.ps1:1174 char:32
1> + ... cFilePath = Get-ProjectsAssociatedNuSpecFilePath -ProjectFilePath $Pr ...
1> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1> + CategoryInfo : NotSpecified: (:) [Get-ProjectsAssociatedNuSpecFilePath], MethodInvocationException
1> + FullyQualifiedErrorId : ArgumentException,Get-ProjectsAssociatedNuSpecFilePath


deadlydog wrote Apr 29 at 5:09 PM

Hmmm, I haven't tried this myself yet either. It's odd that the network path only starts with one backslash instead of 2, as typically a network path is in the form \\Some\Network\Path, but maybe it's different on a Mac?

I'll try and do some testing on my end using network paths and see if I can get it to work. Thanks for reporting the issue :)

johnfager wrote May 9 at 2:25 PM

I don't know why it outputs like that in there. The path is indeed something like \Mac\AllFiles\FileStore\GitHub. For all purposes, it is a Windows network path. Being o the Mac shouldn't affect it.