Export (0) Print
Expand All
1 out of 5 rated this helpful - Rate this topic

Window Class

Provides the ability to create, configure, show, and manage the lifetime of windows and dialog boxes.

Namespace: System.Windows
Assembly: PresentationFramework (in presentationframework.dll)
XML Namespace:  http://schemas.microsoft.com/winfx/2006/xaml/presentation

[LocalizabilityAttribute(LocalizationCategory.Ignore)] 
public class Window : ContentControl
/** @attribute LocalizabilityAttribute(LocalizationCategory.Ignore) */ 
public class Window extends ContentControl
LocalizabilityAttribute(LocalizationCategory.Ignore) 
public class Window extends ContentControl
<Window>
  Content
</Window>

The point of interaction between a user and a standalone application is a window. A Windows Presentation Foundation (WPF) window consists of two distinct areas:

  • A non-client area, which hosts the windows adornments, including an icon, title, System menu, minimize button, maximize button, restore button, close button, and a border.

  • A client area, which hosts application-specific content.

A standard window is shown in the following figure:

Window elements

Window encapsulates the ability to create, configure, show, and manage the lifetime of both windows and dialog boxes, and provides the following key services:

Lifetime Management: Activate, Activated, Close, Closed, Closing, Deactivated, Hide, IsActive, Show, SourceInitialized.

Window Management: GetWindow, OwnedWindows, Owner.

Appearance and Behavior: AllowsTransparency, ContentRendered, DragMove, Icon, Left, LocationChanged, ResizeMode, RestoreBounds, ShowInTaskbar, SizeToContent, StateChanged, Title, Top, Topmost, WindowStartupLocation, WindowState, WindowStyle

Dialog Boxes: DialogResult, ShowDialog.

Additionally, Application exposes special support for managing all of the windows in an application:

  • Application maintains a list of all the windows that are currently instantiated in the application. This list is exposed by the Windows property.

  • By default, MainWindow is automatically set with a reference to the first Window that is instantiated in an application. This thereby making the window the main application window.

A Window can be implemented using markup, markup and code-behind, or code.

Window is primarily used to display windows and dialog boxes for standalone applications. However, for applications that require navigation at the window level, such as wizards, you can use NavigationWindow instead; NavigationWindow derives from Window and extends it with browser-style navigation support.

NoteNote:

Islands of navigable content can be incorporated into other content and content containers using Frame.

Window needs UnmanagedCode security permission to be instantiated. This has the following consequences:

  • ClickOnce-deployed standalone applications will request permission elevation when launched from either the Internet or LocalIntranet zones.

  • XBAPs that request anything less than full permissions will not be able to instantiate windows or dialog boxes.

See Windows Presentation Foundation Security for a discussion on standalone application deployment and security considerations.

Content Model: Window is a ContentControl, which means that Window can contain content such as text, images, or panels. Also, Window is a root element and, consequently, cannot be part of another element's content. For more information about the content model for Window, see Content Control Content Model.

The following example shows how a standard window is defined using only markup:

<Window 
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    Title="Main Window in Markup Only" 
    Height="300" 
    Width="300" />

The following example shows how a standard window is defined using only code:

using System;
using System.Windows;

namespace CSharp
{
    public partial class CodeOnlyWindow : Window
    {
        public CodeOnlyWindow()
        {
            this.Title = "Main Window in Code Only";
            this.Width = 300;
            this.Height = 300;
        }
    }
}

The following example shows how a standard window is defined using a combination of markup and code-behind.

<Window 
    x:Class="MainWindow"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    Title="Main Window" 
    Height="300" 
    Width="300" />

using System;
using System.Windows;
public partial class MainWindow : Window
{
    public MainWindow()
    {
        InitializeComponent();
    }
}

System.Object
   System.Windows.Threading.DispatcherObject
     System.Windows.DependencyObject
       System.Windows.Media.Visual
         System.Windows.UIElement
           System.Windows.FrameworkElement
             System.Windows.Controls.Control
               System.Windows.Controls.ContentControl
                System.Windows.Window
                   System.Windows.Navigation.NavigationWindow
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Windows 98, Windows Server 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.

.NET Framework

Supported in: 3.0
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.