The WeakReference is one of those fun interview topics. Some people have never heard of it and when they learn about it will say, ''That's a textbook question ... why would I ever use a Weak Reference?'' A weak reference references an object while still allowing that object to be reclaimed by garbage collection. Why would you want to do that? ...

We have explored using dependency properties and attached properties to abstract behaviors and triggers. In my last article, TextBox Magic, I showed how to create a dependency property to enable a textbox filter that would prevent anything but digits. In this article, we'll take it a step further and turn it into a ''true'' behavior. A ''true'' ...

So far we've explored how to use dependency properties and attached properties to create reusable behaviors and triggers. I showed you recently how to refactor an attached property to use the Behavior base class instead. Today, we'll look at the TriggerAction that is also available in System.Windows.Interactivity (either as a part of Expression ...

The TextBox control is popular in Silverlight but comes with a few nuances. For example, the default behavior is that the data is not bound until the control loses focus! This can be awkward when you have a form with a disabled save button. The save button won't enable until the text box contains content, but it won't ''know'' about the content ...

One of the most powerful benefits of Silverlight is that it uses the DependencyProperty model. Using this model, you can create attached properties to describe reusable behaviors and attach those behaviors to certain elements. An example of this is firing animations in the UI elements. One criticism of Silverlight has been the lack of support ...