Assembly: PresentationFramework (in PresentationFramework.dll)
XMLNS for XAML: http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/netfx/2007/xaml/presentation
A typical Windows Presentation Foundation (WPF) application may perform a variety of initialization tasks when it starts up, including:
Processing command-line parameters.
Opening the main window.
Initializing application-scope resources.
Initializing application-scope properties.
You can declaratively specify the main window and application-scope resources using XAML (StartupUri and Resources, respectively). Sometimes, however, the resources or main window of your application can only be determined programmatically at run time. Additionally, application-scope properties and command-line parameters can only be used programmatically. Programmatic initialization can be performed by handling the event, including the following:
Initialize application-scope resources by using the Resources property.
Initialize application-scope properties by using the Properties property.
Instantiate and show one (or more) windows.
If you set StartupUri using XAML, the main window that is created is not available from either the MainWindow property or the Windows property of the Application object until after the event is processed. If you need access to the main window during startup, you need to manually create a new window object from your event handler.
If your application uses CredentialPolicy to specify a credential policy, you need to set CredentialPolicy after is raised; otherwise, WPF sets it to a default internal policy directly after the event has been raised.
The command-line arguments that are passed to the event handler are not the same as the URL query string parameters that are passed to an XAML browser application (XBAP).
The following example shows how to acquire and process command-line options from a standalone application. If the /StartMinimized command-line parameter was provided, the application opens the main window in a minimized state.
XAML browser applications (XBAPs) cannot retrieve and process command-line arguments because they are launched with ClickOnce deployment (see Deploying a WPF Application (WPF)). However, they can retrieve and process query string parameters from the URLs that are used to launch them.
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.