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 for Bug 13751 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 4537 [details]
Pic of random nesting issue
My files are mysteriously being nested under other files. There seems to be no rhyme or reason to it. They can be any .cs from anywhere in my solution. Moving them back out to their root folder has no effect. The next time I open the ide, there they are again. See attached screenshots...
Is there any way to reproduce this?
I don't do anything to reproduce it. I come in one day and they are all nested. And it seems to randomly add one from time to time.
I keep making this suggestion but it falls on deaf ears. You guys really need to create some large projects with multiple layers of folder/files and work with it on a daily basis. Yes, it will be costly, but it will uncover these bugs.
It seems that most of these issues involve large scale, complex projects.
We're not ignoring the suggestion. We edit Xamarin Studio in Xamarin Studio, and the core solution has 10336 C# files and 72 projects...
Come on now that is not the same thing. Business apps are totally different animals. Nothing makes total sense in a business app :)
Also note that moving them back to the root does not work. they pop back in the next time.