Kilitli VS 2010 XAML IntelliSense not working

  • 19 Nisan 2010 Pazartesi 09:47
     
     

    XAML intellisense is not working anymore in the final version

    In Tools Options Text Editor XAML Auto list members and Parameter information are Disabled.

    Any solutions ?

    Thank's

    P.S.

    In fact all my navigation pages (from an old RIA app) don't have Intellisense.

    New Pages have .

     

     


    Sorin Sandu
    • Taşıyan Brittany Behrens [MSFT] 20 Nisan 2010 Salı 02:01 Not a designer question, but XAML-specific. (From:Visual Studio Editor)
    •  

Tüm Yanıtlar

  • 26 Mayıs 2010 Çarşamba 03:30
     
     
    I'm experiencing the same problem. Strangely intellisense works for me and then intermittently stops working. Just recently I tried to look at this setting under the Toos > Options > Editor > XAML and it appears that these intellisense options are not checked and are also disabled so I can't check the setting.
  • 26 Mayıs 2010 Çarşamba 13:14
     
     

    Yeah I got the same. Neither my old pages nor new pages have no intellisence. Ctrl+Space not working at all.

    Any ideas? Those "devenv /setup" or "devenv /resetskippkgs" will not do a miracle.

  • 26 Mayıs 2010 Çarşamba 15:47
    Sahip
     
     

    Those Tools->Options settings for XAML are unused and therefore unchecked and disabled all the time, so you don't need to worry about that.

    The best test to see if there is a general problem is to simply create a new WPF Application project and see if you get any IntelliSense. If you do, then there is something going on with your project. Either way, the best way to see what's happening is to attach the debugger of another instance of VS and watch the Output window for exceptions while trying to invoke the failing XAML Intellisense.


    Marco Goertz \ Sr. Dev Lead \ WPF/SL Designer "Cider" \ Microsoft
  • 11 Temmuz 2010 Pazar 02:11
     
     

    I did this and it isn't showing me any issues.  I am using Visual Studio 2010 Premium, Version 10.0.30319.1 RTMRel, .NET 4.0.30319 RTMRel.  Is there any other solutions for this..... it is in my xaml, created a new project and it was working fine.  I would prefer not to remove my xaml line by line to find the issue.

  • 14 Temmuz 2010 Çarşamba 14:45
    Sahip
     
     
    Like I said, if that's the case then you should attach the debugger of another instance of VS and watch the Output window for exceptions while trying to invoke the failing XAML Intellisense. Let me know what you see.
    Marco Goertz \ Sr. Dev Lead \ WPF/SL Designer "Cider" \ Microsoft
  • 13 Aralık 2010 Pazartesi 20:07
     
     
    I'm having the same problem with VS 2010.  I created a new WPF Project and the intellisense worked fine.  I then attached the debugger from a separate instance of VS and attempted to invoke the intellisense in my project.  The intellisense is still broken, and there was nothing in the output window.  Any other suggestions?
    • Yanıt Olarak Öneren _HY_ 10 Mayıs 2012 Perşembe 22:36
    • Yanıt Önerisini Geri Alan _HY_ 10 Mayıs 2012 Perşembe 22:37
    •  
  • 10 Mayıs 2012 Perşembe 22:45
     
     Önerilen Yanıt
    I had the same problem with VS 2010 during editing WPF xaml, and found a way to fix it. Add something wrong in the xaml file where Intellisense is not working and compile the project that the xaml is assoicated. Double click on the error shown in the error list view. Remove the wrong xaml content and type what  you want to add - Intellisense resumes working.
    • Düzenleyen _HY_ 10 Mayıs 2012 Perşembe 22:50
    • Yanıt Olarak Öneren Alex.Covecube 03 Ağustos 2012 Cuma 20:54
    •  
  • 03 Ağustos 2012 Cuma 20:56
     
     
    I had the same problem with VS 2010 during editing WPF xaml, and found a way to fix it. Add something wrong in the xaml file where Intellisense is not working and compile the project that the xaml is assoicated. Double click on the error shown in the error list view. Remove the wrong xaml content and type what  you want to add - Intellisense resumes working.

    Had the same problem. This fixed it.

    Looks like a bug in VS 2010.