Core Silverlight Assemblies and Namespaces
Like any .NET technology, Silverlight is represented by several assemblies. The Visual Studio WPF project
templates automatically set references to the necessary assemblies. Like any other .NET application, you are
able to reference additional assemblies via the Add Reference dialog.
The following key libraries are automatically referenced when creating a new Silverlight project with Visual
Studio. Remember, these libraries are not identical to their .NET 3.5 counterparts.
Although these assemblies provide hundreds of types within numerous namespaces, consider this partial list
of key namespaces. These namespaces are particular to Silverlight projects. Notice that these namespaces
begin with System.Windows, which can be confusing, as you are not building a desktop Windows application!
Recall that Silverlight is indeed based on numerous WPF technologies, and therefore shares similar naming
conventions.
In addition to these Silverlight centric namespaces, recall that Silverlight 2.0 ships with a subset of the .NET
3.5 base class libraries. A full list of each supported namespace can be found under the .NET Framework
Class Library for Silverlight section of the Silverlight 2.0 documentation.
You will work with a number of these namespaces during your lab time, however here is a partial list to spark
your interest:
• System, System.Linq, System.Collections, System.Collections.Generic, System.
Threading: Core expected functionality.
• System.IO, System.IO.IsolatedStorage: Provides safe access to the client side file system.
• System.Reflection, System.Reflection.Emit: Provides dynamic discovery and composition of
types.
• System.Security.*: Numerous namespaces for securing a Silverlight web plug-in.
• System.ServiceModel.*: Numerous namespaces for WCF functionality.
• System.Xml, System.Xml.Linq: Provides an XML based programming model.
Like any .NET technology, Silverlight is represented by several assemblies. The Visual Studio WPF project
templates automatically set references to the necessary assemblies. Like any other .NET application, you are
able to reference additional assemblies via the Add Reference dialog.
The following key libraries are automatically referenced when creating a new Silverlight project with Visual
Studio. Remember, these libraries are not identical to their .NET 3.5 counterparts.
Although these assemblies provide hundreds of types within numerous namespaces, consider this partial list
of key namespaces. These namespaces are particular to Silverlight projects. Notice that these namespaces
begin with System.Windows, which can be confusing, as you are not building a desktop Windows application!
Recall that Silverlight is indeed based on numerous WPF technologies, and therefore shares similar naming
conventions.
In addition to these Silverlight centric namespaces, recall that Silverlight 2.0 ships with a subset of the .NET
3.5 base class libraries. A full list of each supported namespace can be found under the .NET Framework
Class Library for Silverlight section of the Silverlight 2.0 documentation.
You will work with a number of these namespaces during your lab time, however here is a partial list to spark
your interest:
• System, System.Linq, System.Collections, System.Collections.Generic, System.
Threading: Core expected functionality.
• System.IO, System.IO.IsolatedStorage: Provides safe access to the client side file system.
• System.Reflection, System.Reflection.Emit: Provides dynamic discovery and composition of
types.
• System.Security.*: Numerous namespaces for securing a Silverlight web plug-in.
• System.ServiceModel.*: Numerous namespaces for WCF functionality.
• System.Xml, System.Xml.Linq: Provides an XML based programming model.
Core Silverlight Assemblies and Namespaces
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials
|
|
Services