Deborah's Developer MindScape

         Tips and Techniques for Web and .NET developers.

November 4, 2013

XAML Intellisense

Filed under: C#,VB.NET,Visual Studio,XAML @ 9:52 am

In Visual Studio 2013, there were quite a few changes/enhancements to XAML Intellisense. Prior posts covered the most noticed new features … this post covers some of the other changes to Intellisense for XAML.

Prior posts on XAML Intellisense:

This post covers:

  • Fuzzy Matching
  • Camel Case Matching
  • Substring Matching

Fuzzy Matching

Fuzzy matching finds XAML element and attribute names, even if you mistype them.

In the screen shot below, typing "Stakpa" picked up StackPanel.


I tried several other common typing mistakes and was unable to get this to work consistently. It seems that it needs the first few characters to be correct.

In the screen shot below I just missed the "t" and got this:


Camel Case Matching

Camel case matching allows you to type the first letter of each "word" in a name to find it in Intellisense.

Though this is called camel case matching, it also uses Pascal case matching since the majority of the elements and attributes are Pascal cased.

In the screen shot below, I typed "SP":


Substring Matching

Substring matching finds names using a substring search.

In the screen shot below, I typed "Box":


This finds the first occurrence of Box anywhere in the string.

But this is a find and not a filter. So it does not filter the list to all elements containing "box". It just advances to the first match. And there is no way to get to the next match.

Use these features as you work with XAML to more quickly select the element or attribute you want from Intellisense.


For more information on the many new Visual Studio 2013 features, check out my new Pluralsight course: Mastering Visual Studio 2013.

RSS feed for comments on this post. TrackBack URI

Leave a comment

© 2022 Deborah's Developer MindScape   Provided by WPMU DEV -The WordPress Experts   Hosted by Microsoft MVPs