Bug 17039 - ALL images/resources are reset to Build:Content !!!
Summary: ALL images/resources are reset to Build:Content !!!
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Windows
: Normal major
Target Milestone: ---
Assignee: vsx
Depends on:
Reported: 2014-01-03 09:22 UTC by Andy
Modified: 2014-07-18 07:26 UTC (History)
7 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 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 Andy 2014-01-03 09:22:09 UTC
Just opening the project (and saving it) set all the resources to Build:Content !!! 

Now I know what to do for the next few hours. Go through every single image/resource folder and reset them to Build: BundleResource !!!

Yes, I know it's beta, but c'mon !!
Comment 1 Andy 2014-01-06 05:25:45 UTC
Let me add that as much as I tried, it never happened again. However I think this happened in one of the many instances where VS with xamarkn projects hangs and crashes
Comment 2 dean.ellis 2014-01-06 05:33:08 UTC
Hi Andy

Thanks for the info, I will attempt to replicate the issue and see what happens.

Comment 3 dean.ellis 2014-01-06 09:36:08 UTC
Sorry , I am unable to replicate it. That's probably because I've not seen the same crashes or hangs you are seeing. Will continue to investigate
Comment 4 Andy 2014-01-06 09:40:57 UTC
I would have expect it wasn't a common thing, however maybe this is similar to other bugs I reported where resources and configurations were lost or reset. Also because the VS plugin tends to crash/freeze a lot. Actually, it used to do that, nowadays a lot less
Comment 5 Marek Habersack 2014-01-07 09:00:29 UTC
I strongly suspect it has to do with the project being stored on a network share and http://msdn.microsoft.com/en-us/library/dd409252%28v=vs.110%29.aspx this .net setting.
Comment 6 Andy 2014-01-07 09:30:18 UTC
Ok I'll keep them on the PC.

Side note: if we are supposed to keep the solution on the PC, it would make sense to add all the project preferences to VS too, like xcassets, etc