Search

Source: The Code Project

When using the Silverlight Tree View Control, you will discover that it is not easy to expand a Tree Node programmatically without using code behind. This article shows how to do that using a Behavior.

We tweet all news and content updates - follow us on Twitter! 

Source: The <silver/> method

There has been a lot of debate around what to do with collections of Model objects live under a ViewModel. Consider the situation where a Person has a collection of Nicknames and you have created a PersonViewModel. The debate centers around whether you should expose the Nicknames to binding directly, or if you should create a collection of NicknameViewModels to which binding should occur.

We tweet all news and content updates - follow us on Twitter! 

Source: Shawn Wildermuth's Blog

The phone is a small platform (no pun intended) so your Silverlight apps may be smaller than you might imagine. In addition, you are tied to the page navigation story (a good thing IMHO) so you may want to look at handling view-models in a different way.

Source: The Code Project

In the Silverlight Debate Forum project, the developers asked for two way communication, and they wanted it to be 'blendable', meaning, they could use Microsoft Expression Blend, to easily select ICommands and set properties in any View Model control, from any View Model control.

The end result, allows you to call any Master or Child control, from any Master or Child control.

Source: The Imaginative Universal

The Anchor ViewModel pattern described in part 2 of this series is especially well adapted to Hub style layouts where related user controls are organized under a common parent. For instance, a Pivot Control can have a MainViewModel object assigned to its DataContext. If the MainViewModel class has properties with additional ViewModels, for example DetailsName, DetailsAddress, and so on, each of these properties can be used as the DataContexts of the Pivot Items contained in it.

Last week I needed a CheckBoxList control and a RadioButtonList control for Silverlight 4.  I was surprised that they weren’t already part of the standard controls or the Silverlight Control Toolkit.

We will start of with the Creating Multiple Dynamic View Models using the Tab Control project. We add a DueDate field to the Tasks table that is nullable. We will alter the View so that it has a “Due Date” field and permits these operations:

• Indicates when a valid date is not entered
• Allows you to not enter a date at all

With using "View Model Style" programming it may be a little confusing as to how you can communicate between View Models. There are various methods available, but this article explores what I hope to be an easy simple method.

View Model Style allows a programmer to create an application that has absolutely no UI (user interface). The programmer only creates a View Model and a Model. A designer with no programming ability at all, is then able to start with a blank page and completely create the View (UI) in Microsoft Expression Blend 4 (or higher).

The reason for this tutorial, is that I have noticed my friends are getting stuck when trying to learn Silverlight. They spend a lot of time "learning about Silverlight" but have a hard time actually getting started.

I also wanted to show them how to use View Model Style programming because I believe that using View Model, you will write LESS CODE (you probably didn't expect that one!). Don't believe me? Let me show you...

http://www.codeproject.com/KB/silverlight/RIATasks.aspx