As explained in XML vs XAML intellisense section of my blog post, Xamarin 4 ships with an XML-based intellisense for Xamarin.Forms we wrote from scratch. We have worked with Microsoft to make it possible to use the excelent built-in XAML language service instead, which knows about XAML’s specifics, and is driven by metadata provided by the Xamarin.Forms library.
In Visual Studio Update 1, a number of key issues were resolved that make the XAML language service quite usable for Xamarin.Forms XAML editing, so we’re releasing a Visual Studio extension to enable experimental support for it so that we can gather early feedback on what works and what doesn’t. Please file bug reports at our Xamarin Bugzilla tracker, for the
Visual Studio Extensions product, under the
You need to be using the latest stable version of the Xamarin.Forms nuget package, which contains the XAML language metadata required to provide intellisense.
We are providing this extension as an early preview and to gather feedback about things that should be improved or don’t work as expected. So please give it a shot and let us know how it works!
How do you tell if XAML language service is editing your file and not the XML language service?
If your XAML document contains an XML declaration, it will be in blue collor, rather than red:
(you can play “spot the other difference too ;))
Will this break anything on my stable dev environment?
Luckily, this is a minimally disruptive extension that just provides a bit of registry information to Visual Studio to know that it’s safe to open Xamarin.Forms XAML files with the XAML language service, that’s all. For additional reassurance, I’ve just put the extension source in GitHub if you rather see for yourself ;).
Given that, if anything breaks badly, recovery steps are:
- File a bug report!
- Uninstall the
Enable XAML Language for Xamarin.Formsextension from Visual Studio’s Extension Manager (or Extensions and Updates dialog nowadays).
And you’ll be back to normal.
Thanks and please let us know how it works!