locked
the name '' does not exist in the current context RRS feed

  • Question

  • I have a Windows Store App written in XAML/C#.  I have named several item in my XAML code.  In my code behind, I get the error:

    the name '<object name>' does not exist in the current context

    When I rebuild, the errors go away until I make even the slightest change then they all come back.  This prevents me from using intellisense when I am manipulating the named objects in the code behind.  Does anyone know a trick to fix this?

    Thanks,

    Jim


    Jim Wilcox

    Wednesday, December 4, 2013 7:11 PM

All replies

  • I see this in my own VS.  It's a bug and is being tracked.

    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

    Wednesday, December 4, 2013 9:28 PM
    Moderator
  • Matt

    Any ETA on a fix for this?

    Or a workaround?

    It is very frustrating :-(

    Thanks.

    Philip

    Saturday, June 21, 2014 3:13 PM
  • It is not nearly as bad since I have applied Service Pack 2 to VS 2013.

    Jim


    Jim Wilcox

    Sunday, June 22, 2014 3:01 PM