Bug 42655 - Login Screen Component Build
Summary: Login Screen Component Build
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bill Holmes
Depends on:
Reported: 2016-07-19 14:00 UTC by chance8007
Modified: 2016-07-22 15:26 UTC (History)
1 user (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 chance8007 2016-07-19 14:00:04 UTC
Error	1	Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.DirectoryNotFoundException: Could not find a part of the path "\\staff00user\m\Documents\Visual Studio 2013\Projectslocal\Components\loginscreen-1.4.1\samples\LoginScreen.Android.Sample\obj\Debug\__library_projects__\Xamarin.Controls.LoginScreen.Android\library_project_imports\__res_name_case_map.txt"	LoginScreen.Android.Sample
Comment 1 Bill Holmes 2016-07-22 15:26:01 UTC
I was not able to reproduce this error.  

It does not appear that this is a MAX_PATH issue as the length is only 224.  I attempted to reproduce with the elements that make this patch interesting.  On a network share with spaces in the path.

Does the error still occur for you if you copy the solution locally?  Does the __res_name_case_map.txt file actually exist when you see the error?  Also be sure that you are using the latest version of Xamarin tools.

Please reopen if you are able to find more details