Bug 15366 - Can't build app more than once if I had an error on the list
Summary: Can't build app more than once if I had an error on the list
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-10-11 16:04 UTC by Iliass Yousfi
Modified: 2015-08-24 10:57 UTC (History)
6 users (show)

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

VS2012 About Info (54.14 KB, image/png)
2013-10-18 16:59 UTC, Iliass Yousfi

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 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 Iliass Yousfi 2013-10-11 16:04:26 UTC
I am using a demo xamarin.android with shinobi using visual studio 2012.
When I ran the first time everything works fine.
But if suddenly i had made a syntax mistake (an error in the error list), Then even if I correct it I will get this error :
Error	1	Unexpected error - Please fill a bug report at http://bugzilla.xamarin.com. Reason: System.IO.DirectoryNotFoundException: Could not find a part of the path "C:\Users\iyousfi\Downloads\ShinobiCharts Android Trial 1_0_0\ShinobiCharts Android Trial 1.0.0\Xamarin.Android\samples\ShinobiQuickStart\obj\Debug\__library_projects__\Com.ShinobiControls.Charts\library_project_imports\Com.ShinobiControls.Charts.Jars.shinobicharts-android.jar"	C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets	617	2	ShinobiQuickStart

This error will stick there and make the project impossible to build. Even if I close the project keeping visual studio open it will not be removed.
Only when I quit VS 2012, and reopen the project then I can build
Comment 1 Iliass Yousfi 2013-10-18 16:59:40 UTC
Created attachment 5174 [details]
VS2012 About Info
Comment 2 Prashant manu 2013-11-21 01:47:59 UTC
Today we have tried this issue with the following builds and able to rebuild project successfully after correcting a syntax error.

Environment Details:
All windows
VS 2012/2013
Xam.Android 4.10.01073


Please try again with latest version of Xamarin.Android 4.10.01073.
Comment 3 Enzo Heredia 2015-06-30 12:47:21 UTC
not reproducible in XMA build
Comment 4 Rajneesh Kumar 2015-07-15 14:43:47 UTC
@ Iliass Yousfi, I have checked this issue with the latest stable build XVS 3.11.666 and observed that I am also not able to reproduce this. 

Screencast:  http://www.screencast.com/t/6NeRFd3L

Could you please check this issue with the latest stable build XVS 3.11.666 and let us know its working for you OR you are till getting same behavior ?


Environment Info:

Microsoft Visual Studio Professional 2013
Version 12.0.31101.00 Update 4
Microsoft .NET Framework
Version 4.5.50938
Installed Version: Professional
Xamarin   3.11.666.0 (ebae43a)
Visual Studio extension to enable development for Xamarin.iOS and
Xamarin.Android (5f55a9ef61c11b6ce0890bc91e4c71b1b92be214)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS (67b390d0d1bd741582cf7b7fd3ffea08583a3f83)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 5 Rajneesh Kumar 2015-08-05 10:36:16 UTC
There is no response from the reporter. So as of now I am closing this issue against stable build XVS 3.11.666. Please feel free to reopen this issue if you again facing this behavior at your end.

Hence Closing this issue.