Too long deployment path

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.

This post was most recently updated on January 27th, 2019.

This post describes a few different ways of fixing the 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.” one can get when trying to package/publish a SharePoint solution, web site or an Azure Webjob.

UPDATE 11.4.2016: I actually got this nasty exception on another occasion (Azure webjob publish), so I updated the text accordingly!

Symptoms

Visual Studio throws the following error when packaging a SharePoint solution to a .wsp file, OR when deploying or publishing your web project (for example Azure Webjob).

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.

So, what to do to fix this?

Solution

Depending on the type of your project, the right solution might be just a bit different – although the error seems to be thrown by msbuild during the build/publish action in any case. And just like the error says, it’s because a step in the process is failing because it’s trying to use a folder that’s located in a path that’s too long.

How to fix SharePoint Solutions in Visual Studio?

We’ll need to get the feature’s deployment path to be shorter. This applies to AT LEAST the typical, Classic SharePoint solutions:

  1. Full-trust solutions
  2. sandboxed solutions and
  3. add-in projects.
Too long a deployment path highlighted in Visual Studio - this is not going to work.
Too long a deployment path highlighted in Visual Studio – this is not going to work.

If it’s actually about just a few characters (and it often is), you can try the following solution:

How to change a feature’s deployment path in Visual Studio?

  1. Open the feature’s extended settings by double-clicking it’s name
  2. Select “Deployment path”. You should see something like “$SharePoint.Project.FileNameWithoutExtension$_$SharePoint.Feature.FileNameWithoutExtension$”
  3. Remove the first token, or replace it with a short name describing your project or solution.
  4. Save and build/package/deploy.
  5. The problem should be gone now.

This should ix the issue for your typical SharePoint projects. But what about other types of projects or solutions in Visual Studio?

How to resolve the issue for other project types?

In case you’re publishing a webjob or other web project, or the difference is not by just a few characters, you could also try the following steps.

How to change the path for the build process’s temporary files?

  1. Unload your web/webjob project
  2. Select “Edit [yourprojectfilename].csproj
  3. Add the following entry under the first <PropertyGroup> that exists in the xml file:
    1. <IntermediateOutputPath>..\Temp</IntermediateOutputPath>
  4. Reload the project
  5. Clean the project
  6. Try the deployment/publish again – it should work now.

So, what did this do? It quite simply shortened the temporary build/publish output path for Visual Studio, so that it didn’t exceed the 260-character limit. For me, the publish to Azure went fine after this.

In case you STILL encounter this problem, you may have to actually use some slightly blackish magic to map your code to somewhere on your file system where your paths become shorter. Symbolic links might help you – but I never had to go that deep.

More info

Follow me

Antti K. Koskela

Antti Koskela is a proud digital native nomadic millenial full stack developer (is that enough funny buzzwords? That's definitely enough funny buzzwords!), who works as a Solutions Architect for Valo Intranet, the product that will make you fall in love with your intranet. Working with the global partner network, he's responsible for the success of Valo deployments happening all around the world.

He's been a developer from 2004 (starting with PHP and Java), and he's been bending and twisting SharePoint into different shapes since MOSS. Nowadays he's not only working on SharePoint, but also on .NET projects, Azure, Office 365 and a lot of other stuff.

This is his personal professional (e.g. professional, but definitely personal) blog.
Follow me

4
Leave a Reply

avatar
5000
2 Comment threads
2 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
3 Comment authors
http://opera.comAntti K. KoskelaFrans Daniel Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Frans Daniel
Guest

Long path error!
“Long path tool” is very helpful for this problem. You can solve this problem like copy, delete, long path files by using this tool.
I used to have similar problems too, but after using “long path tool” everything was solved.

http://opera.com
Guest

Hey just wanted to give you a quick heads up. The text in your post seem to
be running off the screen in Internet explorer. I’m not sure if this is a formatting issue or something to do with
browser compatibility but I thought I’d post to let you know.

The layout look great though! Hope you get the issue
resolved soon. Many thanks