Bug 56827 - Build failes because path too long
Summary: Build failes because path too long
Status: RESOLVED DUPLICATE of bug 30147
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 7.3 (15.2)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2017-05-25 07:49 UTC by Miha Markic
Modified: 2017-05-30 09:15 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Miha Markic 2017-05-25 07:49:55 UTC
The offending line is

2393: <RemoveDirFixed Directories="$(MonoAndroidIntermediate)__library_projects__" Condition="Exists ('$(MonoAndroidIntermediate)__library_projects__')" />


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.

This is an Android project a bit deeper in the directory hieararchy using Compat libraries among others.
OS is Windows 10, VS 15.2.
Comment 1 dean.ellis 2017-05-30 09:12:32 UTC
This is a duplicate of 30147.

unfortunately there isn't too much we can do about extending the max path length of windows. That said we are trying to look into figuring out a way to shorted the paths for those intermediate libraries. But we have to do it in such a way that it is compatible. For now the best advice is to move the project closer to the root of the drive. e.g 


*** This bug has been marked as a duplicate of bug 30147 ***
Comment 2 Miha Markic 2017-05-30 09:15:45 UTC
Windows 10 is supposed to do wonders with path length :).
Can you elaborate where exactly is the problem, please?