Infrastructure. Security Critical. Enables a native Silverlight host, such as Expression Blend or Visual Studio, to instruct Silverlight to register an assembly that the Silverlight host has separately loaded into the host-managed application domain in which a Silverlight application is running.

The markup for application manifests is technically XAML. However the various elements for manifests are not included in the typical default Silverlight XML namespace (http://schemas.microsoft.com/winfx/2006/xaml/presentation). Instead, the manifest elements are mapped to the http://schemas.microsoft.com/client/2007/deployment XML namespace.

Generally, you do not have to change the XAML in an application manifest if the project specifies that each build should generate the application manifest. In contrast to the very basic usage shown in the XAML Object Element Usage section above, a typical Deployment would also specify additional attributes, and might also contain property elements for Parts, ExternalParts, and OutOfBrowserSettings.

You can retrieve a Deployment object in managed code through the Current property. This gives you read-only access to the deployment settings. To set deployment values, you must modify the AppManifest.xaml file deployed with your application package.

In Visual Studio, the AppManifest.xaml file is generated by the build based on information that you specify in the project designer. For more information, see Silverlight Page, Project Designer.

By default, the build generates the AppManifest.xaml from a template in the Properties folder named AppManifest.xml. You can specify values in the manifest template or you can disable manifest generation to provide your own AppManifest.xaml file. This is useful, for example, to specify non-default values for the RuntimeVersion and ExternalCallersFromCrossDomain properties.