Bug 17749 - Project messed up again - Updated to ?
Summary: Project messed up again - Updated to ?
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.2.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2014-02-13 10:30 UTC by Andy
Modified: 2017-03-07 11:31 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 Andy 2014-02-13 10:30:40 UTC
No clue if it's the update, OR/AND the VS Plugin. No clue about anything really.

what I know is that when I reopened the project today there were quite a few resources (images, sounds, etc) which were EXCLUDED from the project. 

This happens periodically, maybe 10 times, again not sure if it's the update. It's just very annoying on top of all the other bugs.

One time all my resources build action were reset. A few times it lost stuff. And a LOT of times it messed up the info.plist.

I wasted way too much time investigating your bugs so far (I submitted 60 and before you ask again, no, I don't work for you), so please don't ask for screenshots, test cases, etc. If you don't want to look into it, simply keep a reminder that your load/save procedure on either XS or VS is somehow BROKEN.
Comment 1 Marius Ungureanu 2014-12-10 23:06:28 UTC
Is this report supposed to be about Xamarin.iOS? If so, does it still happen?
Comment 2 Vsevolod Kukol 2017-03-07 11:31:01 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!