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.
There appears to be a bug in the editor. When there are 2 Layout xmls with the same name in 2 folders, double clicking one, then the other gives you the same file.
If you Right click and choose Open with Source Code Editor, it's fine.
For images and more see my SOF post:
Installation UUID: 438ac2b5-07c9-45e7-a8ce-eac5ad86371d
Mono 2.10.9 (tarball)
Package version: 210090011
Apple Developer Tools:
Xcode 4.5 (1839)
Mono for Android: 4.2.6
*** This bug has been marked as a duplicate of bug 6302 ***
Today, with the latest builds:
We have followed the below mentioned steps:
1. Created the new MFA template application.
2. Added the new folder with the name "layout1" under the resources folder, so
that two folders appears under the resources folder: "layout" and "layout1".
3. Now add a new android layout with the same name as the present one:
"Main.axml" in the folder "layout1"
4. Observe that the fresh empty file Main.axml automatically updates itself to
contain the content of the "Main.axml" appearing in the folder "layout"
Which shows that the issue still exists.
However, if we add another layout with the different name such as "Main1.axml",
then the changes are saved only to the one which is opened.
Not changing the status of the issue, as we are not sure about the correct
PJ look into it and confirm the correct behavior and let us know about the
further course of action for this issue.