Build works - but 'The fully qualified file name must be less than 260 characters' in VSBuild.ps1 v1.0.013 about azure-pipelines-tasks HOT 8 CLOSED

I am quite sure this is due to the node packages. We are steadily working on fixing the things we can but some of the underlying issues in the .NET framework are hitting us. Some customers are working around that by deleting all of the node packages at the end of each build.

from azure-pipelines-tasks.

OK, no worries. If there's anything I can do, let me know.

from azure-pipelines-tasks.

Any update on this? I am facing the same issue. I checked my solution and do not see any files with long filepaths or names..Additional information on pointing the filenames that are violating the rules will be helpful.

from azure-pipelines-tasks.

Do you have a node_modules directory or something else that has long paths?

From: shanavt [mailto:[email protected]]
Sent: Friday, September 4, 2015 10:23 AM
To: Microsoft/vso-agent-tasks [email protected]
Cc: Chris Patterson [email protected]
Subject: Re: [vso-agent-tasks] Build works - but 'The fully qualified file name must be less than 260 characters' in VSBuild.ps1 v1.0.013 (#377)

Any update on this? I am facing the same issue. I checked my solution and do not see any files with long filepaths or names..Additional information on pointing the filenames that are violating the rules will be helpful.

—
Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fMicrosoft%2fvso-agent-tasks%2fissues%2f377%23issuecomment-137749484&data=01%7c01%7cChris.Patterson%40microsoft.com%7cc740b90c0cc844f508b308d2b53464fa%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=I44p%2bUQaGMSIyg8VWcZJsMEIWf8bnq%2fQlDAXUR2e8d4%3d.

from azure-pipelines-tasks.

Yes.. I have Bower Components..

from azure-pipelines-tasks.

As a workaround, try using npm3. The node_modules folder structure is flat by default.

Since doing this a lot of our path headaches have gone away.

from azure-pipelines-tasks.

Here's what I had to do to resolve this issue:

• Update the VSBuild and MSBuild tasks using tfx
• Update the agent from the TFS web interface
• Use npm 3.2.2 on the build server
• Delete existing workspaces from the build agent's _work folder, just to clean up super-deep npm 2.x-style directories

This takes care of that error when 'restore NuGet packages' is checked. Using a wildcard solution name is a different story though, because even with npm 3.2.2, some node_modules are still just too long. For example, bower 1.6.5 still has a deep dependency branch. So to bite the remaining issues, just be sure to explicitly specify the solution/project files' names on your MSBuild/VSBuild tasks.

from azure-pipelines-tasks.

MSBuild/VSBuild tasks have been fixed to handle long paths in the 1.95 agent. The deployment is rolling out over the course of the next couple weeks. Your agent will need to be updated to 1.95 to get the fix (will happen automatically when the agent is restarted, otherwise can perform via the admin web UI).

from azure-pipelines-tasks.