It saves you from having to explicitly set the design time DataContext on the data template. If you choose to specify the DataContext in code-behind you can set the design-time DataContext in the view and we will able to piggyback off that for resolving properties in binding expressions.įurthermore for getting binding IntelliSense in resources like data templates which may be defined in external resource dictionaries you can either choose to set the design time DataContext on the data template or if you navigate to the data template using Go To Definition (F12) we will do the work required to copy the right DataContext over.
In order for the editor to resolve the properties we require the data context to be specified on the view and not set in code-behind. IntellISense for properties of the current data context is now available in binding expressions. This blog post describes the new editor features in detail and how you can use them! IntelliSense for Data Binding Your feedback was heard loud and clear and we have taken a crack at the top XAML editor feature requests in Visual Studio 2013. While many of you like creating XAML using our visual tools, many prefer creating XAML in the code editor as well.
0 kommentar(er)
