General

• Single - you can select only one item.

Silverlight 3 enables property binding to CLR objects and other UI components via XAML – UI to UI binding. It is useful in a lot of scenarios and saves time for both developers and designers.

Example

Download source code

Syntax

{Binding Value, ElementName=MySlider}

where Value is property of a CLR object and MySlider is the name of this object

Hope that helps!

Have you ever noticed that the MouseLeftButtonDown and MouseLeftButtonUp events are not fired when a Silverlight button is clicked? The reason for this is that the button handles these two events itself by overriding the OnMouseLeftButtonDown  and the OnMouseLeftButtonUp  handlers. In the OnMouseLeftButtonDown  override the Click event is raised and the MouseLeftButtonDown event is marked as handled so it couldn't bubble in the visual tree. The OnMouseLeftButtonUp  override also marks the MouseLeftButtonUp  as handled.

When using the object element to display our Silverlight application, we can use parameters to configure it (source, onerror, background, minRuntimeVersion and etc.):

<object data="data:application/x-silverlight-2," type="application/x-silverlight-2" width="100%" height="100%">

    <param name="source" value="ClientBin/Issues.xap"/>

    <param name="onerror" value="onSilverlightError" />

    <param name="background" value="white" />

    <param name="minRuntimeVersion" value="2.0.31005.0" />

    <param name="autoUpgrade" value="true" />

    <a href="http://go.microsoft.com/fwlink/?LinkID=124807" style="text-decoration: none;">

         <img src="http://go.microsoft.com/fwlink/?LinkId=108181" alt="Get Microsoft Silverlight" style="border-style: none"/>

    </a>

</object>

Some of them are predefined in the automatically created TestPages, but we can also add additional parameters like initParams, onload and etc.

Just use the following line.

C#

Application.Current.Host.Content.IsFullScreen = true;   

Entering full-screen mode in Silverlight has some restrictions. To ensure that it is initiated by the user entering full-screen mode is possible only in response to one of these input events: MouseLeftButtonDown. MouseLeftButtonUp, KeyDown, KeyUp.

That's it!

The callback function of a routed event has the second parameter e of type RoutedEventArgs or its inheritor. The Source property of this parameter holds reference to the object that raised the event. In contrast to that the sender parameter holds reference to the object where the event handler was invoked.

C#

void RoutedEventRaised( object sender, RoutedEventArgs e )

{

    object source = e.Source;

}

That's it!

Some of the new features in C# 3.0 allow you to write shorter code that is easier to read and maintain. The following code couples have the same results.

• Short syntax for object initialization initialization.

  C#

   

  ObjectType objectName = new ObjectType();

  objectName.PropertyName = newValue;

  objectName.PropertyName2 = newValue2;

   

  C#

  ObjectType objectName = new ObjectType(){ PropertyName = newValue, PropertyName2 = newValue2 };

• Syntaxt for anonymous types

C#

SomeVeryLongNameOfType objectName = new SomeVeryLongNameOfType();

C#

var objectName = SomeVeryLongNameOfType();

• Short syntax for collection initialization

C#

CollectionType collectionName = new CollectionType();

collectionName.Add( newItem1 );

..

Probably the first most important thing to mention here is that only inheritors of System.Windows.DependencyObject can be extended with attached properties. This is needed because either to set or to get value for a specific attached property, you need to use the methods SetValue and GetValue which are defined in the DependencyObject class.
When you declare an attached property, many advantages from the dependency properties model are coming out of the box for you such as caching, data binding, default values, expressions, styling, property invalidation and more.