In Visual Studio 2015 Preview, you can now peek and edit definitions from XAML. Let’s take a look at some examples from Lilly Notes, a WPF application I built upon WPF MDI.
You can Peek Definition in your XAML editor via a context menu when right-clicking, or by pressing Alt+F12:
If you do that on an event handler, you can peek into the event handler’s definition in the codebehind, without ever leaving your XAML:
For more extended editing, you can “Promote to Document” (see screenshot above) to open the actual code file.
If you have an ElementName binding, you can peek into the definition of the target element, as you can see below with ToggleEditTitleButton:
XAML Peek also works pretty nicely with resources, which may be scattered about your project. For instance, I’m using this BoolToHiddenConverter as a StaticResource. I can peek its definition in the UserControl’s Resources section:
As it turns out, I can also peek the resource’s type (in this case BoolToVisibilityConverter), to edit the converter directly:
No doubt this feature will be pretty handy for those writing some of the larger WPF or Windows Phone 8 applications.
Another of the IDE enhancements you’ll find in Visual Studio 2015 Preview is that unused using directives (C#) or imports (VB .NET) will appear in a less prominent colour, to distinguish them from the usings/imports that are actually used.
You can see an example of this when creating a new WPF application (screenshot above), since most of the usings provided by default in the codebehind are useless until you require specific WPF features.
That’s not all, however. On the side, you’ll find a light bulb that will suggest remedial actions. In this case, it’s suggesting that you remove the unused usings. When you hover over this action, you actually get a preview of what your code will look like.
You’ll see more of this paradigm of suggested actions and live previews as I continue to cover the new features in Visual Studio 2015 Preview.