Personally I hate this file because it can cause a lot of trouble if it gets corrupted.
And since it is hidden, you don’t always think about it.
So the rule is: If you see some weird behavior in Visual Studio, try to delete the SUO file first, before you try anything else.
Update: I was just told that unloading and reloading the project file might help too.
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.
Metadata in SSMS isn't updating unless I shut it down and restart.
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 component.
For the auto-update of _you can disable by setting the flag to 'false' To install Angular JS Intellilsense add on, run the following command in the Package Manager Console 1.0.3 - set min ref to 1.3 and less than 1.4 1.0.1 - minor fix - polluted _file 1.0.0 - initial release DISCLAIMER: This package is maintained by Shawn Cicoria, but is based upon the hard word of John Beldsoe who created the Intellisense support for Angular JS in Visual Studio.
As explained in XML vs XAML intellisense section of my blog post, Xamarin 4 ships with an XML-based intellisense for Xamarin. 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. In Visual Studio Update 1, a number of key issues were resolved that make the XAML language service quite usable for Xamarin.
Set value to "Disable" to prevent default Intelllisense from parsing at all.