"Path too long" when publishing asp.net 5 from Visual Studio 2015

Question

This seems to be a common problem and I found several Stack Overflow questions, but they all seem to pertain to MSBuild.

I'm trying to publish by right-clicking on my asp.net 5 rc1 project in Visual Studio and invoking a file system-based publish profile.

Its settings look like this:

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <WebPublishMethod>FileSystem</WebPublishMethod>
        <LastUsedBuildConfiguration>Release</LastUsedBuildConfiguration>
        <LastUsedPlatform>Any CPU</LastUsedPlatform>
        <SiteUrlToLaunchAfterPublish />
        <LaunchSiteAfterPublish>True</LaunchSiteAfterPublish>
        <ExcludeApp_Data>False</ExcludeApp_Data>
        <CompileSource>False</CompileSource>
        <_DefaultDNXVersion>dnx-clr-win-x86.1.0.0-rc1-final</_DefaultDNXVersion>
        <UsePowerShell>True</UsePowerShell>
        <IISCommand>web</IISCommand>
        <WebRoot>wwwroot</WebRoot>
        <WwwRootOut>wwwroot</WwwRootOut>
        <IncludeSymbols>False</IncludeSymbols>
        <Native>False</Native>
        <IgnoreDNXRuntime>False</IgnoreDNXRuntime>
        <publishUrl>C:\Source\CCollections\artifacts\bin\CCollections.Client.Web.Angular\Release\PublishOutput</publishUrl>
        <DeleteExistingFiles>False</DeleteExistingFiles>
    </PropertyGroup>
</Project>

This yields this output:

C:\Source\CCollections\src\CCollections.Client.Web.Angular>C:\Users\Christopher\.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-final\bin\dnu.cmd publish "C:\Source\CCollections\src\CCollections.Client.Web.Angular" --out "C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96" --configuration Release --runtime dnx-clr-win-x86.1.0.0-rc1-final --wwwroot "wwwroot" --wwwroot-out "wwwroot" --iis-command "web"
Microsoft .NET Development Utility Clr-x86-1.0.0-rc1-16202

Executing script 'prepublish' in project.json
npm WARN package.json ASP.NET@0.0.0 No description
npm WARN package.json ASP.NET@0.0.0 No repository field.
npm WARN package.json ASP.NET@0.0.0 No README data
npm WARN package.json ASP.NET@0.0.0 No license field.
npm WARN unmet dependency C:\Source\CCollections\src\CCollections.Client.Web.Angular\node_modules\gulp-cssmin\node_modules\gulp-util requires minimist@'^0.2.0' but will load
npm WARN unmet dependency C:\Source\CCollections\src\CCollections.Client.Web.Angular\node_modules\gulp-cssmin\node_modules\minimist,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency C:\Source\CCollections\src\CCollections.Client.Web.Angular\node_modules\gulp-cssmin\node_modules\through2 requires readable-stream@'~1.0.17' but will load
npm WARN unmet dependency C:\Source\CCollections\src\CCollections.Client.Web.Angular\node_modules\gulp-cssmin\node_modules\readable-stream,
npm WARN unmet dependency which is version 1.1.13
[12:15:37] Using gulpfile C:\Source\CCollections\src\CCollections.Client.Web.Angular\gulpfile.js
[12:15:37] Starting 'clean:js'...
[12:15:37] Starting 'clean:css'...
[12:15:37] Finished 'clean:js' after 8.17 ms
[12:15:37] Finished 'clean:css' after 7.58 ms
[12:15:37] Starting 'clean'...
[12:15:37] Finished 'clean' after 6.63 μs
[12:15:38] Using gulpfile C:\Source\CCollections\src\CCollections.Client.Web.Angular\gulpfile.js
[12:15:38] Starting 'min:js'...
[12:15:38] Finished 'min:js' after 14 ms
[12:15:38] Starting 'min:css'...
[12:15:38] Finished 'min:css' after 3.02 ms
[12:15:38] Starting 'min'...
[12:15:38] Finished 'min' after 6.03 μs
[12:15:40] Using gulpfile C:\Source\CCollections\src\CCollections.Client.Web.Angular\gulpfile.js
[12:15:40] Starting 'libcopy'...
[12:15:40] Finished 'libcopy' after 19 ms
Copying to output path C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96
Using Package dependency Microsoft.AspNet.DataProtection.Abstractions 1.0.0-rc1-final
Using Package dependency Microsoft.CodeAnalysis.CSharp 1.1.0-rc1-20151109-01
Using Package dependency Microsoft.AspNet.Identity 3.0.0-rc1-final
Using Package dependency Microsoft.Extensions.Configuration.CommandLine 1.0.0-rc1-final
Using Package dependency Microsoft.Extensions.Logging.Console 1.0.0-rc1-final
Using Package dependency System.Runtime.InteropServices 4.0.0
Using Package dependency System.Diagnostics.Debug 4.0.0
Using Package dependency Microsoft.AspNet.Mvc.Razor.Host 6.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Mvc.Razor.Host\6.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Mvc.Razor.Host\6.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\System.Runtime.InteropServices\4.0.0
Using Package dependency EntityFramework.Commands 7.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\EntityFramework.Commands\7.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\EntityFramework.Commands\7.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.CodeAnalysis.CSharp\1.1.0-rc1-20151109-01
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Extensions.Configuration.CommandLine\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Configuration.CommandLine\1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.DataProtection.Abstractions\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.DataProtection.Abstractions\1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\System.Diagnostics.Debug\4.0.0
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\System.Diagnostics.Debug\4.0.0
Using Package dependency Microsoft.AspNet.Mvc.TagHelpers 6.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Mvc.TagHelpers\6.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Mvc.TagHelpers\6.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.CodeAnalysis.CSharp\1.1.0-rc1-20151109-01
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\System.Runtime.InteropServices\4.0.0
Using Package dependency Microsoft.Extensions.Configuration.EnvironmentVariables 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Extensions.Configuration.EnvironmentVariables\1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Extensions.Logging.Console\1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Identity\3.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Identity\3.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Configuration.EnvironmentVariables\1.0.0-rc1-final
Using Package dependency Microsoft.AspNet.Diagnostics 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Diagnostics\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Diagnostics\1.0.0-rc1-final
Using Package dependency EntityFramework.Core 7.0.0-rc1-final
Using Package dependency Microsoft.AspNet.Mvc.ViewFeatures 6.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Mvc.ViewFeatures\6.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Mvc.ViewFeatures\6.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Logging.Console\1.0.0-rc1-final
Using Package dependency Microsoft.Dnx.Compilation.Abstractions 1.0.0-rc1-final
Using Package dependency Microsoft.Extensions.Configuration.FileExtensions 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Extensions.Configuration.FileExtensions\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Configuration.FileExtensions\1.0.0-rc1-final
Using Package dependency Microsoft.AspNet.Identity.EntityFramework 3.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Identity.EntityFramework\3.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\EntityFramework.Core\7.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\EntityFramework.Core\7.0.0-rc1-final
Using Package dependency System.Diagnostics.DiagnosticSource 4.0.0-beta-23516
Using Package dependency Microsoft.Extensions.Logging.Debug 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Extensions.Logging.Debug\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Logging.Debug\1.0.0-rc1-final

Using Package dependency Microsoft.AspNet.Diagnostics.Abstractions 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.Diagnostics.Abstractions\1.0.0-rc1-final
Using Package dependency Microsoft.AspNet.PageExecutionInstrumentation.Interfaces 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.AspNet.PageExecutionInstrumentation.Interfaces\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.PageExecutionInstrumentation.Interfaces\1.0.0-rc1-final
Using Package dependency Microsoft.Extensions.Configuration.FileProviderExtensions 1.0.0-rc1-final
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Dnx.Compilation.Abstractions\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Dnx.Compilation.Abstractions\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Identity.EntityFramework\3.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.AspNet.Diagnostics.Abstractions\1.0.0-rc1-final
Using Package dependency System.Text.Encoding 4.0.0
    Source C:\Users\Christopher\.dnx\packages\System.Text.Encoding\4.0.0
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\System.Text.Encoding\4.0.0
    Source C:\Users\Christopher\.dnx\packages\System.Diagnostics.DiagnosticSource\4.0.0-beta-23516
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\System.Diagnostics.DiagnosticSource\4.0.0-beta-23516
    Source C:\Users\Christopher\.dnx\packages\Microsoft.Extensions.Configuration.FileProviderExtensions\1.0.0-rc1-final
    Target C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Configuration.FileProviderExtensions\1.0.0-rc1-final
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

C:\Source\CCollections\src\CCollections.Client.Web.Angular>

I think my problem is here: C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\

I need to use a shorter path, like C:\Temp.

I've tried some of the suggestions in other stack overflow answers.

Adding <AspnetCompileMergeIntermediateOutputPath>c:\shortPath\</AspnetCompileMergeIntermediateOutputPath> to the profile doesn't appear to help.

Adding <IntermediateOutputPath>..\Temp</IntermediateOutputPath> doesn't seem to work either.

I'm guessing it's because these settings get picked up by MSBuild, but not dnu publish.

So how to I tell dnu publish to build the package in C:\Temp instead of my appdata directory?

Update: Finding the culprits: I think the files that exceed the path limit are not in the above log, and that only the successful copies are logged. To test this hypothesis:

I deployed to c:\temp by running dnu publish manually
Copied the files from c:\temp to C:\Users\Christopher\AppData\Local\Temp\PublishTemp
Ran a script to iterate all files recursively and output path lengths that exceed 248 characters. Results:

C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Configuration.FileProviderExtensions\1.0.0-rc1-final\lib\net451\Microsoft.Extensions.Configuration.FileProviderExtensions.dll

File path long: 249 chars

C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96\approot\packages\Microsoft.Extensions.Configuration.FileProviderExtensions\1.0.0-rc1-final\lib\netcore50\Microsoft.Extensions.Configuration.FileProviderExtensions.dll

File path long: 252 chars

The biggest folder is 191 characters, and with the file it's 252 characters, so that's not exceeding 240 and 260 characters, respectively.

Regardless of all this, how do I tell Visual Studio 2015 to use "C:\temp" as its temp directory, instead of my profile's temp directory?

At what stage of the publish does this happen? Does this happen when your node packages are being installed? — Dealdiane, Nov 20 '15 at 18:01
If I watch the path `C:\Users\Christopher\AppData\Local\Temp\PublishTemp\CCollections.Client.Web.Angular96` with Explorer during the execution of `dnu publish`, I see folders such as `Microsoft.AspNet.PageExecutionInstrumentation.Interfaces` showing up in approot/packages immediately before I get the error. — Christopher, Nov 20 '15 at 18:04
Could you post the output of your dnu publish? Also, you can change the output by `dnu publish -o `. — Dealdiane, Nov 20 '15 at 18:13
Have you tried the `-o` (or `--output` if you want to be explicit) switch? — Dealdiane, Nov 20 '15 at 18:21
That's an alias for `--out`, which I am already using. I understand the nature of this error, and deploying to a shorter path like `c:\inetpub\site` works fine when I run this command manually. My question is how do I get Visual Studio to supply a different directory when I use its publishing feature. It's using that long temp directory and I don't know how to tell it to execute `dnu publish` with a different, shorter, temp directory. — Christopher, Nov 20 '15 at 18:23
The longest string (path + file name) in your output is only 176 characters - well short of the 260 // 248 maxpath boundary. I've had trouble with paths that had "."s in them, and I see one of your directories is labeled: "CCollections.Client.Web.Angular96" thus. That may be an issue. I also have problems with %20 - or spaces sometimes. Usually these problems come from files created on Unix-based (Linux) systems and then ported over to Windows. — SRQ Coder, Nov 20 '15 at 19:00
Interesting observation. To test my hypotheses that only the successful copies are logged, I conducted an experiment and added the results to my post. There are two paths that are over 248 characters. — Christopher, Nov 20 '15 at 19:12

score 34 · Accepted Answer · answered Nov 20 '15 at 20:41

34

Change the temp output to a path with a shorter path name.

Open your target .pubxml in .\Properties\PublishProfiles from a text editor.
Change or add an element called PublishOutputPathNoTrailingSlash under PropertyGroup and set the value to your desired path.

<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <PublishOutputPathNoTrailingSlash>C:\Temp\Publish</PublishOutputPathNoTrailingSlash>
  </PropertyGroup>
</Project>

answered Nov 20 '15 at 20:41

Dealdiane

3,984
1
24
35

That works! It uses that path for the temp files, but still goes where I want it to ultimately. – Christopher Nov 20 '15 at 20:49
3

If you ever visit Dallas, I will buy you a beer. – Christopher Nov 20 '15 at 20:57
2

If you ever visit London, I will buy you a beer. – Skorunka František Dec 08 '15 at 22:18
1

If you ever visit Sydney, I will buy you a beer. – mnsr Jan 14 '16 at 03:22
1

If you ever visit Moscow, I will buy you some vodka. – Cool Breeze Feb 01 '16 at 03:08
3

If you ever visit Paris, I know someone that will buy you a beer – wilovent Feb 10 '16 at 13:17
1

If you ever visit Melbourne, I'll buy you a slab. – Maverick Mar 16 '16 at 03:23
1

If you ever visit Brazil, I'll buy you a capirinha. – Apr 05 '16 at 21:13
1

I like checking this answer every couple months to see where in the world @Dealdiane gets free stuff. – Christopher Apr 27 '16 at 16:09
1

If you ever visit Latvia, I'll buy you some great potato with your name on it! +bonus: this deal available for @Chris too. – briiC May 16 '16 at 07:32
1

This doesn't help me too much because I'm using a web Project, but ... Hey if you visit Zaragoza(Spain) i will buy you a beer. – jlsfernandez May 20 '16 at 09:51
If you ever visit Belgium, I will try to find you some security ;) – iBoonZ May 27 '16 at 12:49
If you ever visit India, I will buy you a beer !! – antony.ouseph.k Jul 21 '16 at 08:16
If you ever visit Ukraine, I will buy you a borscht – hluhovskyi Dec 04 '19 at 12:13
if you ever visit jersey I'll buy you a vegan cheesesteak! I didnt use your answer but stumbled upon this and thought I'd extend the great hospitality of New Jersey to you. a world unto itself. – AtheistP3ace Oct 28 '20 at 22:06

score 2 · Answer 2 · answered Apr 15 '16 at 16:53

2

For new asp.net mvc 6 in project.json use

"exclude": [ "wwwroot", "node_modules" ],`
"publishExclude": [ "**.user",  "**.vspscc" ]

answered Apr 15 '16 at 16:53

Борис Вандышев

21
1

score 0 · Answer 3 · answered Nov 20 '15 at 19:56

0

I think this is what you're looking for:

When you go into the "Publish Web' dialog, you'll need to change the 'Target Location' within the "Connection" tab. (Hit the Square Box with ...) and then browse to C:\Temp and your files go there...

The dialog won't allow you to create C:\Temp on the fly, so if you haven't created it already , you'll need to do so beforehand.

I do hope this does it.

answered Nov 20 '15 at 19:56

SRQ Coder

552
5
10

Unfortunately, that doesn't work for two reasons. 1) I do not want to publish to temp. 2) It still fails for the exact same reason because the path it uses as a temp directory (before copying files to c:\temp) is too long. – Christopher Nov 20 '15 at 20:03
What about changing the file path to exclude the dots(.) as in: CCollections.Client.Web.Angular96 ?? – SRQ Coder Nov 20 '15 at 20:09
The problem is that the publish feature uses my windows profile's temp path to construct the files it will ultimately deploy. I do not know where to instruct visual studio to use a shorter path. – Christopher Nov 20 '15 at 20:12
Under "PublishProfiles" in Solution Explorer, there is a an xml file that will allow you to modify the _PublishTargetUrl. Mine looks lilke this: – SRQ Coder Nov 20 '15 at 20:35
Are you using asp.net 5 rc1? As you can see in my original question, I do not have those items. When you execute the publish, is your output log showing "dnu publish"? – Christopher Nov 20 '15 at 20:38
My Dev machine is Win 10 asp.net 5 1.0.0-rc1-final...Underneath the project within 'src', there is a 'Properties' folder. Inside of that is the PublishProfiles folder. inside of thhta is a file with a .pubxml extension. Under that file is one with the .pubxml.user extension. That's where I was able to change the PublishTargetUrl field. – SRQ Coder Nov 20 '15 at 20:50
Again, that is not the temp folder that it uses. That is the final destination (this is just a user-specific version of it). If you actually did a publish, you would still see C:\Users\Stephen\AppData being used as the temp directory. opiants found the answer, though, so we're good! – Christopher Nov 20 '15 at 20:52

"Path too long" when publishing asp.net 5 from Visual Studio 2015

3 Answers3

Linked