Silverlight Games: Getting the infrastructure down by blowing it out of the browser

In the XAML AppManifest.XML file there is a bunch of arcane symbols and words.  In the previous blog I detailed the high level of how to detach the Silverlight Application.  This is an important part of the future of Silverlight, works in the browser and works out of the browser.  Build once and really use everywhere and every when.  Uggh, just getting examples for the AssemblyPart that is comprehensive is going to take awhile.  Okey dokey, here are the combined links, as you can tell it is mostly cut and paste from MSDN.  Although I did add a few comments here and there.  Anyway, mark this one for the future discussions.

<Deployment xmlns= >


          <AssemblyPart x:Name="xamlName" Source="assembly" />



AssemblyPart Class

An assembly part is an assembly that is to be included in a Silverlight-based application package (.xap).

AssemblyPart Members exposes these members:

AssemblyPart Constructors

    • AssemblyPart, used in managed code, not XAML
AssemblyPart Methods
AssemblyPart Properties
  • Dispatcher: Gets the Dispatcher this object is associated with. (Inherited from DependencyObject.) A dispatcher object  provides services for managing the queue of work items for a thread.  Cannot be directly created in an instance of XAML, it is used only in managed code. (Reference)

  • Source: Gets the Uri that identifies an assembly as an assembly part.  The value of the Source property should be the physical name of the assembly, including the .dll file extension. For example, Application.dll.

Comments (0)

Skip to main content