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 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.
Created attachment 3287 [details]
The Intellisense and text coloring is missing in the axml files. Instead of following the standard XML editor colouring it seems fixed on a grey background, with dark grey text.
Attached are two files. 'Not-Styled' is the 'source view' as standard. The 'Styled' screenshot is if I put the content
into a separate xml file and view in Visual Studio.
Created attachment 3288 [details]
I am also having this problem. I use ReSharper as well but I have disabled it and this still have not fixed the problem.
Is their any fix on the horizon?
From Bug 1871:
Jonathan Pryor 2013-01-28 21:28:06 EST
After this workaround default opening of axml files with Designer is gone.
I have found that it might not be XSD problem and locations of schemas, but
rather VS API for loading file.
After accidentally introducing error in axml I have double-clicked on error in
Error window. Axml opened in XML source editor, but w/o intellisense,
subsequent double-click opened file in xml source editor but WITH intellisense.
*** Bug 7239 has been marked as a duplicate of this bug. ***
Syntax highlighting is there, this is only about intellisense getting confused.
I believe that this was fixed in 4.7.10.
Today we have checked this issue with following builds:
We observed that when we open .axml file using double clicking on .axml and then click on Source tab and then search text using Ctrl+F then it does not search the specified text in .axml file and showing popup like 'File is already open. This is screencast for the same: http://screencast.com/t/rFKiyzH4eO
Hence reopening this issue.
Today we have checked this issue on following builds :
Now we are able to see text color and intellisence in axml file when we use "ctrl + F" key and search some text.
Hence closing this issue. Changing its status to verified.
Prashant, Saurabh: Allie is describing two different methods of opening the file. In one case it works, in the other case it didn't work.
You are both saying you tried the case *that always worked*, so you can't verify with those steps.
1. Create a new Android project
2. Open the .axml file by double clicking on it, then switching to the Source view
3. Begin typing / editing the source of the axml file.
You should get autocomplete and text coloring (the most basic intellisense) when, for instance, deleting and re-writing a line
In the universal monodroid add-in suite: https://testrail.xamarin.com/index.php?/cases/view/58329
Today we have checked this issue with the following builds:
Now Intellisense and text coloring is displayed in the axml file whether user search .axml file with ctrl+F
or user open's .axml file by just double clicking on it.
Below is the screencast for the same:
Hence changing this issue status as a verified.
I'm using Windows 8 and VS 2012. Intellisense is not working when I click the source tab in android designer. If a select open with->automatic editor selector (xml) it works.
This behavior happens in xamarin studio and visual studio.
I'm using Windows 7 and VS2012.
CTRL+F does not search the axml file.
There is no intellisense.
Hence reopening the issue.
tested on VSX 3.1.224 (july) and I am able to use both axml intellisense and Ctrl+F option within editor. Closing bug...
I still have this bug with 220.127.116.11 (VS2013 / Windows7)
CTRL-F still opens the floating "find and replace" box, which does not search the current .axml file.
And intellisense still does not work.