Although the .NET Framework 3.0 technology is still in Beta, it is available for use from Microsoft Corporation. (Go to the xaml.net Links page for Microsoft links for these downloads.) Please read the comments about using Microsoft's Beta technology carefully.

.NET 3.0 Runtime Components are more-or-less updated on a monthly basis. These Components allow you to run .NET 3.0-based applications, run XBAPs and create and save XAML files and XBAPs. To develop on the .NET 3.0 platform, you will require the latest SDK, plus Visual Studio 2005 or the .NET Framework 2.0 SDK.

While .NET 3.0 is a key component of the Vista OS, the Runtime Components will be made available for download as an update for XP and Server 2003 users. (Check back for more details closer to Vista's launch.) These same Runtime Components are also able for redistribution by ISVs.

System Requirements

• Windows XP (SP2), Server 2003 or Vista

• Pentium-class 1GHz CPU (min) and 256 MB RAM (min)

• DirectX 9 hardware accelerated graphics (preferred)

Key Differences: .NET 2.0 to .NET 3.0

What’s so different about WPF and XAML? Find out how XAML makes it easier to create and use next-generation graphics.

#1: In WPF, controls (e.g. buttons) are "first class citizens". This means that the look and feel of controls can be completely changed – their rendering can be overridden – with the use of XAML.

#2: With data binding (in XAML, a "bind declaration"), properties of XAML-based objects can be tied to other objects, Web services or external XML data sources without the use of additional script or codebehind.

#3: WPF has a DocumentView control, which is similar to a PDF viewer, that loads, zooms, and prints any fixed/flow format documents. As this control is also an element, it can be embedded into a XAML document with a simple XAML element tag or used in a .NET form.

#4: A FormsHost element allows legacy ActiveX controls to be embedded into a XAML document.

#5: A ContentHost element allows XAML (and WPF functionality) to be embedded into existing .NET 1.1 applications.

#6: With XAML, a user can generate custom WPF controls. These controls can be created as assemblies and used in the markup like any other shape or control, plus have access to styling and data binding.

Getting Started: Panels for Application UI

In WPF, the following six panels are specifically intended as root layouts for application UIs. In other words, these panel types form the foundation of your XAML document.

Canvas

This panel positions child elements in exact x,y coordinates (0,0) starting from the upper left.

Objects are rendered in the order of their XAML markup. Although this panel type is included as one intended for application UIs, it is not the best choice for a root layout as it is fixed and therefore will not resize. This panel type is better for graphic design / artwork.

DockPanel

This panel arranges child elements horizontally or vertically, relative to each other, within a defined area.

"Dock", which is an attached dependency property, determines whether the elements are placed above, below, to the right or to the left of one another (e.g. depending upon where the element is "docked" in the panel).

Grid

This panel is comprised of adaptable columns and rows.

As precise spacing for columns and rows can be set with this panel (using the Margin property), it is a good option as the root layout for UIs.

StackPanel

This panel is similar to the DockPanel, except that the child elements are stacked within a defined area.

The StackPanel has resizing capabilities that, depending upon how the defined area is resized, will stack the elements either horizontally or vertically.

VirtualizingStackPanel

This panel is similar to the StackPanel, except this option is meant to save memory and processor space when working with a large UI.

The "virtualizing" portion of the StackPanel means that with this type of panel UI elements are created and arranged only for on-screen (e.g. visible) items.

WrapPanel

This panel automatically "wraps" child elements within a defined area.

Elements are wrapped sequentially (depending upon the Orientation property), and break to the next line when they reach the edge of the defined area.

See the xaml.net Resources page for a list of tools that can help you with your WPF/XAML project.