Bug 42552 - Intellisense is not working for custom controls in .axml
Summary: Intellisense is not working for custom controls in .axml
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 6.1.0 (C7)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Stephen Shaw
Depends on:
Reported: 2016-07-14 10:12 UTC by Mohamed Samsudeen
Modified: 2017-01-24 19:15 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

warning in custom layout (25.69 KB, image/png)
2016-07-14 10:12 UTC, Mohamed Samsudeen

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Mohamed Samsudeen 2016-07-14 10:12:28 UTC
Created attachment 16665 [details]
warning in custom layout

Intellisense is not working for custom controls in .axml.

The custom layout which was inherited from ViewGroups like LinearLayout, FrameLayout was added in the .axml file. 
In which I am getting the warning as shown in the attached image. Also, Intellisense for default framework properties is not working.
Comment 1 Stephen Shaw 2016-09-28 20:48:50 UTC
This feature isn't fully available in Visual Studio right now. It should be fix in the near future. I'll update the bug one it is fixed.
Comment 2 Stephen Shaw 2017-01-24 19:15:20 UTC
This will be available in the upcoming cycle9 release.