locked
XAML Intellisense? RRS feed

  • Question

  • User5139 posted

    It appears there is no intellisense when editing a Xamarin.Forms XAML file or did something go wrong with my install? If there is none, is there an XSD that could be used when editing the file in the XML Text editor?

    Friday, May 30, 2014 9:24 PM

Answers

  • User352 posted

    I suspect we will need help from MS to make it happen. Sorry :( The way their tooling works just isn't really compatible with the PCL framework.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Tuesday, June 3, 2014 5:55 AM

All replies

  • User4821 posted

    I'm having the exact same issue. There is no intellisense at all when trying to create a Xamarin.Form. Should there be designer support for this as well as selecting "View Designer" does not do anything.

    Saturday, May 31, 2014 2:41 AM
  • User54846 posted

    I too am having this issue -- the designer does not work and there is no Intellisense. Note: I am using Visual Studio 2013 Update 2

    Saturday, May 31, 2014 10:34 AM
  • User33 posted

    It appears there is no intellisense when editing a Xamarin.Forms XAML file or did something go wrong with my install?

    Are you using ReSharper? There's currently a bug in ReSharper's version of IntelliSense that causes this. Note that you can disable ReSharper's IntelliSense without disabling all of it and without losing smart completion elsewhere.

    Should there be designer support for this as well as selecting "View Designer" does not do anything.

    There is no designer, this option will just have Visual Studio trying to open the .xaml file with its own WPF/WP/WinRT designer which won't work.

    Saturday, May 31, 2014 12:03 PM
  • User54846 posted

    Any thoughts on adding support for the designer? It would make a HUGE value add as it would allow more designers to work on the UI for mobile apps.

    Saturday, May 31, 2014 1:25 PM
  • User54846 posted

    I am using resharper -- what do I need to disable to get this to work?

    Saturday, May 31, 2014 1:30 PM
  • User5139 posted

    I am not using Resharper. Here is the Visual Studio About information:

    Microsoft Visual Studio Professional 2013 Version 12.0.30501.00 Update 2 Microsoft .NET Framework Version 4.5.51641

    Installed Version: Professional

    LightSwitch for Visual Studio 2013 06177-004-0446025-02539 Microsoft LightSwitch for Visual Studio 2013

    Office Developer Tools - May 2014 Update ENU 06177-004-0446025-02539 Microsoft Office Developer Tools for Visual Studio 2013 - May 2014 Update ENU

    Team Explorer for Visual Studio 2013 06177-004-0446025-02539 Microsoft Team Explorer for Visual Studio 2013

    Visual Basic 2013 06177-004-0446025-02539 Microsoft Visual Basic 2013

    Visual C# 2013 06177-004-0446025-02539 Microsoft Visual C# 2013

    Visual C++ 2013 06177-004-0446025-02539 Microsoft Visual C++ 2013

    Visual F# 2013 06177-004-0446025-02539 Microsoft Visual F# 2013

    Visual Studio 2013 Code Analysis Spell Checker 06177-004-0446025-02539 Microsoft® Visual Studio® 2013 Code Analysis Spell Checker Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved. The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

    Windows Phone SDK 8.0 - ENU 06177-004-0446025-02539 Windows Phone SDK 8.0 - ENU

    ASP.NET and Web Tools 2013.2.50425 Microsoft Web Developer Tools contains the following components: Support for creating and opening ASP.NET web projects Browser Link: A communication channel between Visual Studio and browsers Editor extensions for HTML, CSS, and JavaScript Page Inspector: Inspection tool for ASP.NET web projects Scaffolding: A framework for building and running code generators Server Explorer extensions for Windows Azure Web Sites Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Windows Azure

    ASP.NET Web Frameworks and Tools 2012.2 4.1.21001.0 For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

    ASP.NET Web Frameworks and Tools 2013 5.1.20409.0 For additional information, visit http://www.asp.net/

    Common Azure Tools 1.1 Provides common services for use by Azure Mobile Services and Windows Azure Tools.

    File Nesting 1.0 Automatically nest files based on file name and enables developers to nest and unnest any file manually

    Microsoft Team Foundation Server 2013 Power Tools 12.0 Power Tools that extend the Team Foundation Server integration with Visual Studio.

    Microsoft Visual Studio Process Editor 1.0 Process Editor for Microsoft Visual Studio Team Foundation Server

    NuGet Package Manager 2.8.50313.46 NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

    PreEmptive Analytics Visualizer 1.2 Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

    SQL Server Data Tools 12.0.30919.1 Microsoft SQL Server Data Tools

    Web Essentials 2013 1.0 Adds many useful features to Visual Studio for web developers.

    Windows Azure Mobile Services Tools 1.1 Windows Azure Mobile Services Tools

    Windows Phone 8.1 SDK Integration 1.0 This package integrates the tools for the Windows Phone 8.1 SDK into the menus and controls of Visual Studio.

    Workflow Manager Tools 1.0 1.0 This package contains the necessary Visual Studio integration components for Workflow Manager.

    Xamarin 3.0.54.0 (d3cf238e3845e930e312b6ec9b4c6c5437c33067) Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android

    Xamarin.Android 4.12.4.20 (b5dc5ce91305e19de51d71a1122c109719c4bc34) Visual Studio plugin to enable development for Xamarin.Android.

    Xamarin.iOS 3.0.54.0 (d3cf238e3845e930e312b6ec9b4c6c5437c33067) Visual Studio extension to enable development for Xamarin.iOS

    XtraReports package 1.0 XtraReports package

    Saturday, May 31, 2014 1:51 PM
  • User33 posted

    I am using resharper -- what do I need to disable to get this to work?

    ReSharper's IntelliSense should be enough. ReSharper -> Options -> IntelliSense -> General -> Select Visual Studio.

    Saturday, May 31, 2014 1:55 PM
  • User54846 posted

    Tried that -- no luck (Even restarted VS)

    Saturday, May 31, 2014 1:57 PM
  • User40009 posted

    I'm running visual studio pro, update 2 and I have no plugins other than xamarin installed. Any other things I could try to get intellisense to work?

    Saturday, May 31, 2014 9:53 PM
  • User4821 posted

    I've completely disabled resharper but I'm still not getting any intellisense:

    Saturday, May 31, 2014 10:04 PM
  • User55225 posted

    Same here...For now I switched to Xamarin Studio and Intelli-Sense works there.

    SUPER PUMPED about Xamarin.Forms though :)

    Saturday, May 31, 2014 10:46 PM
  • User54846 posted

    Same issue here -- completely turned off Resharper and still not working.

    Monday, June 2, 2014 12:29 PM
  • User29306 posted

    XAML Intellisense has a chance of working if you can open the .xaml file using the Xaml UI Designer editor. When I try to Open With on the .xaml file to select that, I get this error: "The file cannot be opened with the selected editor. Please choose another editor."

    This works fine for opening a Xamarin Forms XAML page if the file is defined in another kind of project (say, a WPF project). It seems that Portable Class Libraries is deliberately denying the ability to use that editor. Note that I'm not expecting the designer to work. But opening any xaml file using that editor tends to make the code editing half of the designer work, including Intellisense. So use linked files to add these xml files to another type of project (say... a WPF project for example) and you can open them in the right editor and you're halfway there.

    Once the editor can be opened, there's another step required for it to work (from my experience getting XAML Intellisense to work on other object models, anyway). You need to help the editor find the types represented by the tags. Some great documentation on this is available on MSDN. First let's look at the XAML produced by the Xamarin Forms' "Forms XAML Page" item template:

    <?xml version="1.0" encoding="utf-8" ?>
    <ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
                           xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
                           x:Class="Dart.MyFormXaml">
        <Label Text="{Binding MainText}" VerticalOptions="Center" HorizontalOptions="Center" />
    </ContentPage>
    

    Notice the root tag has a namespace that is just a URI -- not "clr-namespace" bit. That's fine, but it means some other magic is required to associate the namespace with the assembly that the types come from. For this to work in the designer's code pane, this association comes from the assembly carrying the types. Specifically, the Xamarin.Forms.Core.dll assembly needs to define this attribute:

    [assembly: XmlnsDefinition("http://xamarin.com/schemas/2014/forms", "Xamarin.Forms")]
    

    That attribute is regrettably missing from the assembly, so getting Intellisense to work while the xmlns attribute is the way it is in the item template (I think) is impossible.

    You can preview some of what Intellisense will be like after this work is done (on Xamarin's side) by creating such a .xaml file inside a WPF project, adding the Xamarin.Forms NuGet package to it, and then opening it inside the XAML editor. Change the opening tag to read this:

    <ContentPage xmlns="clr-namespace:Xamarin.Forms;assembly=Xamarin.Forms.Core"
                       xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
                       x:Class="Dart.MyFormXaml">
    

    Notice how I've changed the value of the xmlns attribute. This now tells XAML exactly where to find the ContentPage type, and so Intellisense now works in VS. But since I've changed the xmlns attribute, I expect (although I've not yet tried it) that this may cause deserialization to fail at runtime.

    Monday, June 2, 2014 1:35 PM
  • User33 posted

    Specifically, the Xamarin.Forms.Core.dll assembly needs to define this attribute:

    Given that the Core assembly is PCL and that attribute is defined in System.Xaml.dll, that's a no go. The only way that would work is if the consuming side did a string comparison instead of a type and we could define our own version of the attribute.

    Monday, June 2, 2014 2:39 PM
  • User41050 posted

    The IntelliSense works in Xamarin Studio, how to get it working on Visual Studio 2013? Any one get it working?

    Monday, June 2, 2014 8:12 PM
  • User5139 posted

    Guess I'll use Xamarin Studio for XAML development until they figure out how to get things working in Visual Studio. If things actually work well (binding and performance in particular), I can't describe how excited I am to be able to write XAML for shared UIs.

    Monday, June 2, 2014 8:32 PM
  • User4821 posted

    Any update on this? Has anyone got XAML intellisense working in VS2013?

    Tuesday, June 3, 2014 5:49 AM
  • User352 posted

    I suspect we will need help from MS to make it happen. Sorry :( The way their tooling works just isn't really compatible with the PCL framework.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Tuesday, June 3, 2014 5:55 AM
  • User56091 posted

    Xamarin Studio Intellisense doesn't work and it gives error as soon as I start typing "<" for tag starting. Not using Resharper.

    Any suggestions?

    Thursday, June 5, 2014 4:50 AM
  • User34765 posted

    I would rather have intellisense working before getting a Forms designer in vs.net. Without it, I might as well be typing in Notepad. :(

    Monday, June 23, 2014 9:28 PM
  • User60050 posted

    Intellisense not working. Wish it did. No resharper, fresh install of Xamarin on top of VS2013 update 2.

    Thursday, June 26, 2014 5:19 AM
  • User45818 posted

    I'm going to add a +1 to this. It makes XAML a pretty frustrating experience when there is no IDE support other than color coding. I am using ReSharper, but disabling it doesn't help.

    ReSharper also has some issues with the code behind files.

    Friday, July 11, 2014 4:30 PM
  • User2927 posted

    +1! Tomorrow I have a talk about Xamarin, but will not show so much about XAML because is complicate write XAML without intellicense. And Xamarin Studio only show me Android apps :( and the experience is completly differente.... I prefer VS and Code behide

    Friday, July 11, 2014 10:00 PM
  • User43671 posted

    +1 Presently we have this situation: - VS 2013: Android + iOS + WPhone projects, but no intellisense for XAML - Xamarin Studio: intellisense for XAML, but no iOS or WPhone projects.

    Tuesday, July 15, 2014 3:27 PM
  • User58262 posted

    I'm using Xamarin Studio 5.2 (build 379). From previous update in alpha channel XAML autocomplete has broken. It behaves like in simple XML document. No properties autocomplete and no enums autocomplete. Is it a known bug?

    Thursday, July 17, 2014 1:30 AM
  • User112 posted

    Another wish for XAML Intellisense. Much more important (and probably easier to achive) than Designer.

    Thursday, July 17, 2014 8:36 AM
  • User14 posted

    UserVoice is the place to 'vote' on feature requests - they'll get counted up and summarized for us so we know what to aim for next.

    Thursday, July 17, 2014 7:18 PM
  • User59750 posted

    Thanks @CraigDunn? . I have just suggested a new Idea => http://xamarin.uservoice.com/forums/258559-xamarin-forms-suggestions/suggestions/6187329-xaml-intellisense

    Friday, July 18, 2014 7:50 AM
  • User28769 posted

    In Visual Studio, do the following: Resharper -> Options -> Code Inspection -> Settings -> Edit Items To skip In the "File masks to skip" section, enter *.xaml.cs

    This will cause Visual Studio to recognize the contents of the generated file. Still no intellisense, but at least the editor doesn't complain of missing methods or properties anymore.

    Friday, July 18, 2014 11:21 AM
  • User42013 posted

    @SMouligneaux? I gave my votes! Good idea.

    Friday, July 18, 2014 12:07 PM
  • User58262 posted

    Xamarin Studio 5.2 build 384 still have autocomplete issue in xaml. Is this problem just for me?

    Wednesday, July 23, 2014 2:33 AM
  • User3066 posted

    Adding myself to the list of user asking for Xaml intellisense in Forms.

    Monday, July 28, 2014 9:55 AM
  • User18207 posted

    Same here, +1 for intellisense at least...

    Friday, August 1, 2014 6:12 PM
  • User3571 posted

    +1. Xamarin Forms are really amazing, but without XAML intellisense, it spoils the party

    Wednesday, August 6, 2014 3:16 PM
  • User28549 posted

    Please don't +1 this thread. Instead, if you really want to give your vote, head over to the UserVoice that already has this issue.

    https://xamarin.uservoice.com/forums/258559-xamarin-forms-suggestions/suggestions/6187329-xaml-intellisense

    Wednesday, August 6, 2014 4:35 PM
  • User58262 posted

    Xamarin Studio 5.2 release still broken autocomplete in XAML :(

    Thursday, August 7, 2014 1:52 AM
  • User67900 posted

    It's hard write code XALM without intellisense. Please Xamarin team fix it, it's essential for programmers.

    Thursday, August 7, 2014 9:08 PM
  • User67079 posted

    We are currently qualifying Xamarin for our mobile business strategy and, as of now, even if we understand the potential power of this approach ("one X-Platform design to rule them all"), we have found critical drawbacks (No auto-completion, no online reference documentation with a clear list of attributes like http://developer.android.com/reference/android/widget/TextView.html, ...) that restrain us from using of Xamarin.Forms.

    Friday, August 8, 2014 2:02 PM
  • User14 posted

    @CharlesKEAT.4951? there is API documentation, such as this Entry members page.

    We are aware that people really want auto-complete for Xaml in Visual Studio; and we're also working hard to continually expand the documentation at developer.xamarin.com.

    Friday, August 8, 2014 10:55 PM
  • User11072 posted

    The xaml editor in the code view is just a xml editor so you don't really get intellisense but with the right schema it would sure act like it . If Xamarin provided us with the schema for http://xamarin.com/schemas/2014/forms we could just follow the instructions on the blog post below and fix it the same way we fixed the Visual Studio Android XML editor (This link talks about VS 2012 but it worked fine for me in 2013):

    http://stackoverflow.com/questions/17245308/xamarin-android-intellisense-not-working-in-visual-studio-2010

    With the correct xsd file for http://xamarin.com/schemas/2014/forms this should work nicely for us in Visual Studio. Well for the standard Xamarin.Forms Xaml controls at least.

    Saturday, August 9, 2014 4:39 AM
  • User39749 posted

    Please give us the XSD - 4 months and over 400 votes on uservoice :(

    Tuesday, September 23, 2014 4:46 AM
  • User23746 posted

    I agree... please fix this! After being "sold" on buying the business edition for both iOS and Android turns out that I might as well use notepad to write xaml for Xamarin?! Maybe a change to the website so that it would clarify their statement of "Use the tools, libraries, and design patterns you already know and love, including TFS and ReSharper." would be in order?

    :(

    Thursday, September 25, 2014 11:35 PM
  • User39930 posted

    +1 and voted. I'm having to have a code window open just to get property names and values etc. Really frustrating.

    Wednesday, October 1, 2014 12:02 PM
  • User77668 posted

    :(

    Thursday, October 9, 2014 6:00 PM
  • User80438 posted

    The Xamarin.Forms team absolutely must add this or noone is going to use Xamarin.Forms and the whole thing will be pointless. I certainly ain't paying $999 for something that does not have the absolute basic tools.

    Wednesday, October 15, 2014 9:45 PM
  • User28549 posted

    that's a pretty bold statement there @jonathanyates? (referring to no one and whole thing). I am in fact using XAML and Xamarin Forms in production, and therefore not pointless. I have had to switch into a CS file a couple of times to discover properties, but all-in-all it wasn't that bad.

    I was at Evolve last week and had an opportunity to speak with the entire Forms team... remember, there is only 3 full time devs on that team. They want intellisense just as bad as everyone here, but as it stands, (from what I can remember) they have two options.

    1. write their own complete intellisense engine (paraphrased)
    2. work in conjunction with Microsoft to get intellisense for X.Forms XAML baked into Visual Studio (also paraphrased)

    @ermau, @jasonasmith feel free to correct me.

    Side note (to everyone). Please have patience with your Xamarin.Forms team. They are a very *very* small team, and they can't do everything that we demand. They've undertaken a highly challenging task, and have executed it well. There is of course room for improvement, and no one (including the team themselves) will dispute that, but that doesn't mean that it's open season on them. TL;DR; be nice.

    Wednesday, October 15, 2014 9:54 PM
  • User352 posted

    I want to give an update here because I feel there is a need to clear some air. First @ChaseFlorell? it was wonderful meeting you! Your new forum photo is fantastic also :)

    Intellisense in XS and VS is something that is literally being discussed on the company wide mailing list right now. From XS we are hoping to continue to improve this experience, but I can also say that the majority of people wanted this intellisense want it in VS where you get basically nothing right now. We are working on a three pronged approach there:

    1) The XamarinVS team is working on getting some basic intellisense going. It wont be perfect and might even be wrong at times, but it will be better than zero.

    2) The Xamarin.Forms team is working with Microsoft (or attempting to) in order to resolve any issues with the native XAML tooling with XF integration. Generally speaking it should work, the barriers appear to be purely technical.

    3) The Xamarin.Forms team is working with JetBrains (or attempting to) in order to resolve issues with the JetBrains intellisense engine and Xamarin.Forms. Generally speaking it does work so long as we make a couple minor tweaks, but it has too many false negatives right now to be useful.

    Generally speaking, at least 2 of the 3 of these approaches has to work for us to satisfy users. Even if we fix VS integration, if Resharper remains busted we will have lots of unhappy people (imagine, telling R# users to stop using it, the horror!). It's a BIG problem that unfortunately mostly lives outside or partially outside the realm of our own control. This means changes here are slow as we cant just do it, I wish I had a better answer. This also means I simply cant give you any time estimates.

    We are dedicating just as many resources to this as humanly possible. I hope soon I will have some happy news for everyone, but for now I just have to ask you all to wait patiently and hope you can be understanding.

    Jason Smith

    Xamarin.Forms Lead Engineer

    Wednesday, October 15, 2014 10:06 PM
  • User18207 posted

    Thank you for the feedback guys. Given the explanations I think the reasons why it's not there seems just as fair as the reasons why we ask for it.

    Keep up the good work and thank you for clearing it up for all of us :)

    Monday, October 20, 2014 11:44 AM
  • User40009 posted

    @ChaseFlorell?

    This certainly isn't intellisense ... but XML syntax highlighting and autocomplete for some things can be done with the (overly) large XSD file I've generated and posted on the forums. You can download it over here

    I'm learning XSD stuff as I go so each version is getting smaller and more feature rich. It is a strange side project so no idea when/if I'll finish it... but I use it now and it works well for quite a few things ... It's better than nothing.

    Ryan

    Sunday, November 2, 2014 7:00 PM
  • User5906 posted

    @RyanHatfield? Thank you for excellent solution! I believe problem is one limitation of the Visual Studio Intellisense and not of the Xamarin. However the solution posted to Ryan helped me too!

    Tuesday, January 6, 2015 11:11 AM
  • User5906 posted

    I think the next step is to validate data in the project time. It's too bad you have to debug to validate a XAML code. Also he does not say where the error is. Complicated!

    Tuesday, January 6, 2015 11:15 AM
  • User40009 posted

    @RogerCorrea make sure to check out @kzu 's project here http://www.cazzulino.com/mobileessentials.html

    [EDIT] To be clear I haven't used it, I just keep updating my own version of my XML schema as I see fit.

    Saturday, January 10, 2015 8:34 PM
  • User97322 posted

    Holy crap, RyanHatfield's suggestion works. Intellisense seems to be working with the extension. THANNKKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

    Tuesday, January 13, 2015 3:33 AM
  • User11072 posted

    Always Resharper 9.

    Tuesday, January 13, 2015 12:08 PM
  • User99657 posted

    Just add C:\Program Files (x86)\MSBuild\Xamarin\Android\android-layout-xml.xsd to the XML->Schemas... (this menu will appear as you open axml source).

    Friday, January 16, 2015 5:07 PM
  • User100399 posted

    solution from Ryan Hatfield works great for me, thanks!

    http://www.cazzulino.com/mobileessentials.html

    Sunday, January 18, 2015 5:55 PM
  • User46369 posted

    @5w3crcrsw543dvr you're solution worked and is very simple. Thank you.

    Saturday, February 7, 2015 9:46 PM
  • User4641 posted

    @5w3crcrsw543dvr - I tried your solution but couldn't get it to work for me. Made sure the entry was checked in the Schemas dialog, stopped/started VS 2013 - no joy. Not sure if I missed a step, seemed simple to me.

    I went with @RyanHatfield Mobile Essentials solution and that did the trick for me.

    http://www.cazzulino.com/mobileessentials.html

    Wednesday, February 18, 2015 8:37 PM
  • User6349 posted

    I am also going to throw in a very obvious plug for ReSharper as well. ReSharper pulls its Intellisense from the actual class definitions, no silly, cumbersome XSDs required. :tongue: I have been using it for Xamarin.Forms development for a couple months now and it has been absolutely supreme... and fun! Yeah it costs money, but it is EASILY worth every penny, especially when you open code that has been written by someone who doesn't use it (and it highlights all of the basic code and best-practice violations it contains). You can totally tell when someone uses ReSharper vs. not; it simply helps you to be a better coder all around. Xamarin.Forms Intellisense is just the massive cherry on top! :)

    Thursday, March 19, 2015 10:44 AM
  • User76049 posted

    Another happy Resharper customer and intellisense works very well is VS2013. Totally agree with Mike's comments above, it's well worth the money and you end up writing much cleaner code. We use it in WPF as well. Highly recommend it.

    Thursday, March 19, 2015 1:45 PM
  • User116869 posted

    Solution from Ryan Hatfield works great for me, Thanks! :) http://www.cazzulino.com/mobileessentials.html

    Tuesday, April 7, 2015 12:58 PM
  • User76232 posted

    It works for me, Thanks All.

    Sunday, April 19, 2015 10:50 AM
  • User92851 posted

    The cazzulino solution is not working anymore. It gives 404 error. Any workaround?

    Tuesday, May 12, 2015 11:19 AM
  • User75233 posted

    Latest stable release of Xamarin.Forms (1.4.4.6387) isn't working for me. I have Visual Studio 2013 Update 5 installed with ReSharper Ultimate 2015.1.3 (9.1.3) and my XAML pages cannot resolve the property "Class" in the "http://schemas.microsoft.com/winfx/2009/xaml"; namespace (which then make the whole page a mess). Also when I have a XAML page open in the IDE the compile breaks so I have to close it before I can compile the app. Will try the XSD fix as the extension has been removed from Mobile Essentials as they say it's because there's support in the latest version of Xamarin (which doesn't seem to be the case IMHO).

    Just want to clarify that Intellisense (i.e. editing help) works as shown here:

    However as you can see from the screenshot the XAML markup isn't recognized and suffers from ReSharperSquigglyLineSyndrome.

    Thanks

    Tuesday, July 28, 2015 2:04 PM
  • User148470 posted

    Where I can find the XSD for Xamarin Forms? The Xamarin Installer only provides schemas dor Android AXML.

    Wednesday, August 26, 2015 2:21 PM
  • User98237 posted

    I have pretty much a vanilla VS2015 enterprise install with the Xamarin plugin and am not using Resharper. The intellisense in XAML files is not working.

    Friday, September 4, 2015 7:12 AM
  • User78778 posted

    Use tool Enable XAML Language for Xamarin.Forms https://visualstudiogallery.msdn.microsoft.com/8195a8e2-a842-4389-a8cb-34e4672e2e13

    Tuesday, September 27, 2016 8:10 AM