Error with long paths from Nuget.core codebase

[nmulvihill]

What You Are Seeing?

Long file paths error out due to Nuget.core codebase

What is Expected?

installation of an application with file paths longer than 260 characters

How Did You Get This To Happen? (Steps to Reproduce)

tried installing an application with file paths longer than 260 characters (BMC)

Output Log

Chocolatey v0.10.7
Installing the following packages:
bmc
By installing you accept licenses for the packages.
Progress: Downloading bmc 9.0... 100%
bmc not installed. An error occurred during installation:
The specified path, file name, or both are too long. The fully qualified file n
ame must be less than 260 characters, and the directory name must be less than 2
48 characters.
bmc package files install completed. Performing other installation steps.
The install of bmc was NOT successful.
bmc not installed. An error occurred during installation:
The specified path, file name, or both are too long. The fully qualified file n
ame must be less than 260 characters, and the directory name must be less than 2
48 characters.

Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures

bmc (exited 1) - bmc not installed. An error occurred during installation:
The specified path, file name, or both are too long. The fully qualified file n
ame must be less than 260 characters, and the directory name must be less than 2
48 characters.

relates to issue 934: #934

[ferventcoder]

Thanks for logging this - Added an issue at chocolatey/nuget-chocolatey#15 to reference and will update this issue when that closes. Thanks!

[ferventcoder]

Sorry, wrong button :/

[Iristyle]

Also running across the same problem. I've packaged up the Visual Studio 2017 compiler toolchain into an offline install choco package, but can't get it to actually extract / start the install unless I specify a shorter temp directory..

--cache-location= allows the install to proceed, but the temp directory layout still consumes a good chunk of additional path - i.e. with --cache-location=c:\msvc\ I lose 62 characters in the scratch directory that is calculated like C:\msvc\NuGetScratch\79718448-98f9-4a01-a768-548c06555e8c\locte2r0.oaj\tools where 8 or 10 characters would probably be sufficient.

[tallandtree]

Will this be solved? I've the same issue.

[TheCakeIsNaOH]

This should have been fixed in Chocolatey v2.0.0, as newer NuGet versions directly use System.IO, and those are long path compatible, assuming they are enabled in .Net framework. NuGet/Home#6937

I'm not seeing a reproduction for this issue, so I'm not sure exactly how to test this to confirm that it is definitely fixed.

[corbob]

I think I have some repro very basic steps here:

choco new pkg --version 1.0
rm pkg/tools/*
new-item "pkg/tools/$("$(new-guid)/"*6)file.txt" -force
choco pack pkg/pkg.nuspec
choco install pkg -s .

This is the output from 1.4.0:

And new error from 2.x:

I did also try to find a bmc package, but there doesn't appear to be any on CCR, so had to make my own package. It would be good to get proper reproduction steps and determine if this even was the issue originally reported (this one does feel quite contrived, so would be good to know if there are exampled where this is actually happening).