Saturday, December 27, 2008
Inside AppManifest.xaml
The file contains the following:
<Deployment xmlns="
http://schemas.microsoft.com/client/2007/deployment"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
EntryPointAssembly="HelloSilverlightApp"
EntryPointType="HelloSilverlightApp.App"
RuntimeVersion="2.0.31005.0">
<Deployment.Parts>
<AssemblyPart x:Name="HelloSilverlightApp"
Source="HelloSilverlightApp.dll" />
</Deployment.Parts>
</Deployment>
The manifest specifies the entry point assembly which should be loaded by the Silverlight host and within the assembly it requires a type derived from System.Windows.Application for start executing the application.
Here, the assembly is “HelloSilverlightApp.dll” and type is “App” in the namespace HelloSilverlightApp.
Warning: System.Windows.dll is part of Silverlight and not the one we used for WinForm development.I read in some web sites those explained that XAP also contains a set of required Silverlight assemblies which are needed by this application. But I tried with lot of examples, the XAP contains application's assembly and this manifest. Need to check.
Inside HelloSilverlightApp.dll Assembly
It contains two parts:
The typical .NET type declaration of specific Siverlight application's App and one or more Page. In this example,
HelloSilverlightApp.App
HelloSilverlightApp.Page
Resource: HelloSilverlightApp.g.resources. It contains the declarative artifacts of this application:
page.xaml
app.xaml
Labels: appmanifest, silverlight, xaml
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment