Hi all,
Microsoft released Silverlight 5 first beta (you can download it from here).
Unfortunately it has not so many futures as we probably expected to get in this first drop of Silverlight 5.
This build of the Silverlight 5 includes next top futures:
- XAML Debugging with breakpoints for binding debugging
- Implicit data templates for easy UI reuse
- Double (and multi) click support
- GPU-accelerated XNA-compatible 3D and immediate-mode 2D API
- Low-latency sound effects and WAV support
- Real operating system windows and multi-display support
- Significant performance improvements, fixes and much more
Most of these futures could be used only in Silverlight 5 applications, but not the first one :)
But it's amazing that by installing Silverlight 5 tools for Visual Studio we can get XAML Debugging (Binding Debugging) not only for Silverlight 5 applications but also for Silverlight 4 applications!
Let's try it:
The goal is to build Silverlight 4 based application and try Binding Debugging in it. After we make sure that binding debugging work correctly we will try to run our application on PC which has only Silverlight 4 installed.
1. Create Silverlight 4 application
Let's create Silverlight 4 based application first. Select Silverlight 4 in Silverlight Version combobox:

2. Test Binding Debug
Now let's create some class to which we will bind to and set DataContext of our form:

In xaml we will use simple <Textblock /> to display text stored in SomeString property of the Data class.

Ok, now we all set to start testing Binding Debug.
Place a caret inside binding element and hit F9 to set a break point.
Now start application and see that debugger is able to stop on break point and you could see binding details in Locals window:

Ok, so we are able to use Binding Debugging even with Silverlight 4 applications.
Update: you still can debug Binding in XAML even if your application is built using Silverlight 4 tools only! Try to lunch any application which you have built before installing Silverlight 5 tools and see that you can place a break point in XAML and debugger can stop on that break point and show binding details for you :)