During the Silverlight Firestarter Scott Guthrie gave a preview of Silverlight 5. Based on the list of new features it seems Silverlight 5 will be at least as significant of an update from SL 4 than SL 4 was from SL3.
In this article I’m looking at the 10 most important things any Silverlight developer – like myself – should be excited about in this upcoming release.1. Debug Data Binding Expressions By Using Breakpoints In XAML In Silverlight 4 data binding expressions are great… when you’ve set them up correctly that is. When you want to debug them it’s a real pain to do so. In Silverlight 4 the two ways to debug data binding expressions are:
either to look at the debug output window dump and hope that some relevant information is revealed
or set up dummy ValueConverters so you could your break when the binding actually occurs – if it occurs!
With the ability to be able to place break points in the XAML on binding expressions, none of this hacking will be needed, saving lots of time and frustration. When breaking on a binding a BindingState object is shown in the Locals windows that returns all information on the binding that should help solve the issue with it. Read more: Visiblox
In this article I’m looking at the 10 most important things any Silverlight developer – like myself – should be excited about in this upcoming release.1. Debug Data Binding Expressions By Using Breakpoints In XAML In Silverlight 4 data binding expressions are great… when you’ve set them up correctly that is. When you want to debug them it’s a real pain to do so. In Silverlight 4 the two ways to debug data binding expressions are:
either to look at the debug output window dump and hope that some relevant information is revealed
or set up dummy ValueConverters so you could your break when the binding actually occurs – if it occurs!
With the ability to be able to place break points in the XAML on binding expressions, none of this hacking will be needed, saving lots of time and frustration. When breaking on a binding a BindingState object is shown in the Locals windows that returns all information on the binding that should help solve the issue with it. Read more: Visiblox
Posts
0 comments:
Post a Comment