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.
If a file is marked "dependent" on another file (dragged onto it in the project window), it cannot be moved back outside of its parent without editing the project file. For example, if I drag IWorldLoadable.cs on top of World.cs, it gets moved down a level as a "child" of World.cs. Dragging the file back out of World.cs does not update the project file and reloading the project still displays the file as a child of World.cs. The <DependentUpon> tag must be manually removed in the .csproj file in order to un-parent the file. Additionally, if a child file is deleted or removed from the project, it does not disappear until the project is reloaded; instead, the file turns red.
This was fixed already.
I can still reproduce in 4.2.3_60, which was released after that commit. Did that commit not make the 4.2.3 build?
No, it didn't. I don't think it made 4.2.4 either, but it should be in the next release following that.