Search

Windows Phone 7 (WP7) is the upcoming next generation Mobile Operating System by Microsoft. Amongst the many features, one of the nice features is that it has support for Silverlight. So most of the new features like 3-D, Databinding etc. are now available on WP7. In this article I will explain the basic Databinding as well as 3-D feature on Windows Phone 7. For development of WP7, you can use the VS 2010 Express 2010 for Windows Phone with the Windows Phone Developer Tools.

In Silverlight 4 you can have objects which are the target of bindings as long as they derive from DependencyObject and so ( for me ) what seems a little tiny change where the base class for the target of bindings moves from FrameworkElement to DependencyObject is what allows a designer to sit in Blend and nicely drag/drop my ICommand to the View and have Blend do the right thing.

The canonical example of user settings is a “Show this welcome screen at startup” checkbox so that your application can offer a nice out-of-box experience.

By writing a simple type with some properties, adding a few helper files, and setting up a two-way data binding, you can store any settings without having to write special code.

In my previous post I discussed creating the database and tables for the Silverlight HVP configuration data.  All that was great, and worked just dandy until it was time to get the data from the database server to the application running on the client.

“But,” I thought, “How hard can it be?”  I’ve done a few mini-tutorials… should be straight-forward… And it was… sorta.

The EntitySpaces team blog about their recent support of totally dynamic data binding under Silverlight.

We have managed to pull off something incredibly cool. We now support totally dynamic data binding under Silverlight. EntitySpaces has been gaining a lot of Silverlight fans lately as it really simplifies writing Silverlight applications and our serializable Dynamic Queries under Silverlight just rock. What we have done is akin to implementing ITypedList support for Silverlight (fancy databinding).

Visifire team announced the release of the final version of Visifire v3.0.3 and the major features included in it.

Today we have released the final version of Visifire v3.0.3 which contains the following major features:

• DataBinding.
• IndicatorEnabled property has been implemented for all charts except Pie, Doughnut, SectionFunnel and StreamLineFunnel charts.

Stefan Cruysberghs published an article that covers topics like the new Silverlight designer, the Properties window, design-time properties, binding ViewModel properties, showing data in design-time and some other new Silverlight 4 databinding features.

.NET 4.0 and Visual Studio 2010 offer a lot of new features. Also Silverlight 4 is a major update with many new features (webcam support, RichText control, HTML content, access to local files, drag and drop, ICommand, right clicks and mouse wheel support, COM support, clipboard, unit testing, …). I like all the new features but I was especially interested in improvements that could help my current developments which are based on a M-V-VM architecture with ViewModel properties that are bound to UI controls.

Whenever a new version of Silverlight is released, I start examining its features from two perspectives: how would my current (and planned) LOB applications benefit from using these new features, and what cool new things can I build to entertain my children.

This article will guide you through the process of creating a doodling application (you know, for kids ;)), while covering some of the most visible (or not) new features, coming with Silverlight 4. But this is not just about new features, it’s about how they are prepared and served.

In this post Koen Zwikstra demonstrates how to build your own databinding inspector with the help of Silverlight Spy.

Silverlight Spy is a runtime inspector tool providing a lot of information about your Silverlight application. However, sometimes that information is just not sufficient. Let me explain this with the following use case; you want to have an overview of all databindings that are available in your application and you want to know whether these bindings are valid or not. Silverlight Spy does provide databinding information in its data bindings tab of the property grid, but it doesn't provide a convenient list of all databindings.