Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
I got latest on a project, and for some reason, the csproj file was corrupted, resulting in Xamarin unloading the project and showing the 'corrupt csproj' error as the project node in the solution explorer.
I clicked on the project file, and chose to revert the changes - so that I had the clean server csproj.
This had the unexpected effect of reverting the changes in all the files that would have been in the csproj too!! I lost all my changes!
This isn't how Visual Studio behaves - and Xamarin should probably be consistent with VS here.
This has been fixed and will be included in upcoming releases! Thanks for reporting this!