Composite Application Guidance for WPF ( Prism )
The Composite Application Guidance for WPF is getting nearer and nearer. The June 10, 2008 drop not only includes a renaming of Prim to Composite Application Guidance for WPF and the Prism Library to the Composite Application Library, but the assemblies that ship as a part of the Composite Application Guidance for WPF have now been segmented into their respective roles:
- Microsoft.Practices.Composite.dll. This assembly contains the implementation of the Composite Application Library core components such as modularity, logging and communication services, and several core interfaces’ definitions. This assembly does not contain UI-specific elements.
- Microsoft.Practices.Composite.Wpf.dll. This assembly contains the implementation of Composite Application Library components that target Windows Presentation Foundation applications including commands, regions, and events.
- Microsoft.Practices.Composite.UnityExtensions.dll. This assembly contains the base and utility classes you can reuse in applications created with the Composite Application Library that consume the Unity Application Block. For instance, it contains a Bootstrapper base class —the UnityBootstrapper class— that creates and configures a Unity container with default services when the application starts.
In addition to the Composite Application Guidance for WPF working with Unity there is also a new spike of "Prism" that works with Castle Windsor and Log4Net. Therefore if Unity does not meet your needs, you can use Castle Windsor and Log4Net, which have been around for quite awhile.
Learn more about Composite Application Guidance for WPF here.
Tags:
Prism,
WPF,
WPFCompositeClient