Bug 53399 - [15.1 beta 1][VS 2013] Build Error on building Cheesesquare Android sample on VS 2013(Windows 7 Pro).
Summary: [15.1 beta 1][VS 2013] Build Error on building Cheesesquare Android sample on...
Status: RESOLVED DUPLICATE of bug 30147
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2017-03-16 13:31 UTC by Jacky Waswani
Modified: 2017-03-31 14:18 UTC (History)
6 users (show)

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

Attached logs & screenshot. (257.01 KB, application/x-zip-compressed)
2017-03-16 13:31 UTC, Jacky Waswani

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 Jacky Waswani 2017-03-16 13:31:46 UTC
Created attachment 20380 [details]
Attached logs & screenshot.

On building Cheesesquare sample, (https://github.com/xamarin/monodroid-samples/tree/master/android5.0/Cheesesquare), Build error with following exception observed:
The "ResolveLibraryProjectImports" task failed unexpectedly.
System.IO.PathTooLongException: 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.

Preconditions: Pull the code from https://github.com/xamarin/monodroid-samples/tree/master/android5.0/Cheesesquare.

Microsoft Visual Studio Professional 2013 on Windows 7
Version 12.0.40629.00 Update 5
Microsoft .NET Framework
Version 4.6.01055
Xamarin (a70e3a1)
Xamarin.Android (ff38526)
Xamarin.iOS (49a63dc)

1. Fetch the sample above and open it in the IDE.
2. Build the application.

Actual: Cheesesquare project is throwing exception, while building it.
Expected: Cheesesquare project should build successfully without any error.

Reproducible: 10/10

- Screenshot
- Logs

Screencast link: https://www.screencast.com/t/PZSuMYQUInN3

Note: Above test case successfully passed & executed on Microsoft Visual Studio Enterprise 2013 on Windows 7

Environment Details for system with which issue is not observed:

Microsoft Visual Studio Ultimate 2013
Version 12.0.40629.00 Update 5
Microsoft .NET Framework
Version 4.6.01055
Xamarin (a70e3a1)
Xamarin.Android (ff38526)
Xamarin.iOS (49a63dc)
Comment 1 Juan Marcelo Tondato 2017-03-20 18:19:10 UTC
Moving the bug to Android for visibility from the right team.
Comment 2 dean.ellis 2017-03-21 13:21:48 UTC
This looks like a known issue that happens when projects are creating with a very long path. We usually recommend people work as near to the root drive as possible. e.g c:\Sandbox\myproject.

Where did you check out your project to? 

Are you able provide diagnostic build output for the build? The screen shot while informative doesn't really give us the information we need to investigate this issue.
Comment 3 Roshan Mankani 2017-03-23 09:58:20 UTC
Hello @dean

As per your comment we use the shortest path like "C:\Projects\Cheesesquare" so it was working fine, but when we use long path like "C:\Users\Paras.Ambhore\Desktop\monodroid-samples-master (2)\monodroid-samples-master\android5.0\Cheesesquare" its be a issue.

So I am reverting back the status for this defect to "New" because it is issue.

Please check and let us know if there any more information you need on this defect
Comment 4 dean.ellis 2017-03-31 14:18:50 UTC
This is a duplicate of an existing issue #30147.

*** This bug has been marked as a duplicate of bug 30147 ***