patterns & practices: Composite WPF and Silverlight

Created Issue: Does not support all date formats

smithgp — Fri, 10 Oct 2008 17:23:49 GMT

in the Data/News.xml file, the PublishedDate field throws an exception if the date format is not US (M/D/YYYY) format

Updated Wiki: GettingStarted

ibaumann — Fri, 10 Oct 2008 15:32:26 GMT

Getting Started

Prism 2.0 - First Drop

Version: vNext
Description: Article describing the new features of the first drop of Prism 2.0. This new drop is focused solely on the "multi-targeting" aspects of Prism. Multi-targeting is the ability to build applications that can provide both a WPF desktop and a Silverlight RIA experience by sharing and re-using code and components between the WPF and Silverlight environments.

Use case controllers, container hierarchies and services in composite WPF

Version: 1.0
Description: A summary of use case controllers, container hierarchies and services in composite WPF.

Getting Started with the Composite Application Guidance for WPF

Version: 1.0
Description: Article with overview about what is Composite Application Guidance for WPF.

Composite Application Guidance for WPF (Prism) Tour - Part 1

Version: 1.0
Description: Article with overview about what is Composite Application Guidance for WPF and why or when is necessary. (Part 1)

Composite Application Guidance for WPF

Version: 1.0
Description: Article about the features of the Composite Application Guidance for WPF.

Updated Wiki: Others

ibaumann — Fri, 10 Oct 2008 15:28:51 GMT

Others

MEF - CompositeWPF under one roof

Version: 1.0
Description: Blog post about integrating MEF with CompositeWPF.

Using Spring.NET as IOC container for Composite WPF

Version: 1.0
Description: How to enable Spring.NET as IOC container for Composite WPF.

CompositeWPF - ModuleLoader - a better error handler

Version: 1.0
Description: The current HandleModuleLoadError() error handler buries the actual error in the InnerException property (the lower the level of the error, the deeper it gets buried). This article explains a different approach to handle module load errors to not bury the original error.

Prism, MEF and DI oh my

Version: 1.0
Description: Interview with Glenn Block about Prism and Dependency Injection.

How-to: Use the Disconnected Service Agent (DSA) with CompositeWPF (Prism)

Version: 1.0
Description: Sample application that shows how to use the Disconnected Agent Service Application Block with the Composite Application Library.

Composite Application Guidance for WPF Visual Studio Templates

Version: 1.0
Description: Visual Studio Templates to help developers to start with the creation of a solution using the Composite Application Guidance for WPF.

Composite Guidance for WPF Documentation and Hands On Lab

Version: 1.0
Description: Article that describe the features of the Composite Guidance for WPF Documentation.

Prism How-To: Provide metadata to a view that was placed into a region

Version: 1.0
Description: Approach on how to show a header on a tab using WPF bindings.

Have a Modules View fill Region completely

Version: 1.0
Description: Question on how to make a view fill completely a region.

Updated Wiki: Known Issues / Fixes

ibaumann — Fri, 10 Oct 2008 15:24:08 GMT

Known Issues / Fixes

Bootstrapper initialization is not at the Application Startup event in some of the Quickstarts and Documentation topics

Version: 1.0
Description: Article explaining that the bootstrapper should be initialized in the handler of the Application Startup event.

InvalidOperationException occurs when the same view instance is added to multiple ContentControl regions

Version: 1.0
Description: When the same view instance is added to more than one ContentControl region, an unhandled InvalidOperationException occurs.

Adding same view instance from one region to another region works because WPF allows it

Version: 1.0
Description: Adding a view that exists in one region to another will work, but adding it back to the region it was previously added to will cause an exception.

Problems with StockTraderRI in latest drop???

Version: 1.0
Description: Question about an exception during the loading of the modules due to the CurrentCulture configuration.

Updated Wiki: Migration from CAB

ibaumann — Fri, 10 Oct 2008 15:19:02 GMT

Migration from CAB

Regenerating the WPF/SC-SF Quickstart with the Composite Application Library

Version: 1.0
Description: Article about how the WPF Quickstart (shipped with the Smart Client Software Factory) was regenerated using the Composite Application Guidance for WPF. Includes guidance about how to create the initial solution from scratch, identify the regions, use the Event Aggregator service and load modules..

Interesting in migrating from Composite Application Block (CAB) to CompositeWPF (Prism)? Check our new guidance

Version: 1.0
Description: Guidance that comparesCAB/SCSF based solutions to the Composite Application Guidance for WPF and helps with migration.

Migrate from CAB/SCSF to Composite WPF Guidance / Prism!?

Version: 1.0
Description: Guidance for migrating CAB/SCSF based solutions to the Composite Application Guidance for WPF.

Updated Wiki: Model View ViewModel (MVVM)

ibaumann — Fri, 10 Oct 2008 15:17:43 GMT

Model View ViewModel (MVVM)

Composite WPF - Obtaining View reference with Presentation Model

Version: 1.0
Description: How to obtain a reference to the View through the Presentation Model.

Presentation Model with DataTemplates in CompositeWPF (Prism) Sample

Version: 1.0
Description: Article about a sample application of Presentation Models with DataTemplates on WPF together. The sample is based on the Commanding QuickStart shipped in the first release of the Composite Application Guidance for WPF.

Using the Presentation Model in WPF

Version: 1.0
Description: Information on how the use of templates combined with the Presentation Model pattern can help you build fully testable applications.

First approach to Presentation Model with DataTemplates

Version: 1.0
Description: Presentation Model with DataTemplates.

Updated Wiki: Loosely Coupled Communication

ibaumann — Fri, 10 Oct 2008 15:16:55 GMT

Loosely Coupled Communication

Firing generic events with EventAggregator

Version: 1.0
Description: Article that explains how to fire generic events with Composite WPF (Prism).

Composite WPF - Implementing the SCSF style Event Broker in a CompositeWPF application

Version: 1.0
Description: Article about implementing the SCSF style Event Broker in a CompositeWPF application

Loosely coupled communication - Prism style

Version: 1.0
Description: Loosely coupled communication overview.

Decoupled Communication with Prism (Shared Services)

Version: 1.0
Description: Information on Shared Services.

Decoupled Communication with Prism (Commanding)

Version: 1.0
Description: Information on Composite Commands.

Decoupled Communication with Prism (Event Aggregation)

Version: 1.0
Description: Information on Event Aggregator.

Direction of prism

Version: 1.0
Description: Information on the Event Aggregator implementation.

Event Topics and Wildcards

Version: 1.0
Description: Information on the implementation of events; how to register, publish and subscribe events.

Handling Commands Logic

Version: 1.0
Description: Information on Composite Commands.

Updated Wiki: Commands

ibaumann — Fri, 10 Oct 2008 15:16:00 GMT

Commands

ActiveAware Views and Commands

Version: 1.0
Description: Article describing ActiveAware views and commands functionality in terms of the ability to "Save All" versus "Save Active" scenarios.

ICommand for Silverlight with Attached Behaviors

Version: All
Description: Blog post on how to use commands in Silverlight.

Updated Wiki: UI Composition

ibaumann — Fri, 10 Oct 2008 15:14:41 GMT

UI Composition

Poor man's UI Composition

Version: 1.0
Description: Introduction to UI Composition.

Introducing the dialog workspace for Composite WPF

Version: 1.0
Description: How to create a dialog workspace for Composite WPF.

Updated Wiki: Modularity

ibaumann — Fri, 10 Oct 2008 15:13:40 GMT

Modularity

CompositeWPF - using "Module" configuration files for resolving types

Version: 1.0
Description: Article about automatically loading a module configuration data

CompositeWPF – Installing modules on demand

Version: 1.0
Description: Article about an extended module loader service to make possible on demand installation of modules in a CompositeWPF application. The article shows how to integrate Windows installer functionality and build the module loader service.

Combining module enumerators in CompositeWPF

Version: 1.0
Description: Article about how to make combinations with the Module Enumerators provided by Composite Application Guidance for WPF.

Module status service for CompositeWPF

Version: 1.0
Description: Extension on Composite Application Guidance for WPF that offers the possibility to query a Module status service for a list of available modules and the status of each module.

How to load CAL modules from a website (or other locations)

Version: 1.0
Description: Article about how load assemblies from different locations like from the Web or from a database.

Access the shell from modules

Version: 1.0
Description: Question on how to access the shell from modules. It shows several approaches.

Updated Wiki: Regions

ibaumann — Fri, 10 Oct 2008 15:12:40 GMT

Regions

WindowRegionAdapter for CompositeWPF (Prism)

Version: 1.0
Description: Blog post introducing the WindowRegionAdapter for Composite WPF (with an application sample).

Use the OutlookBar in your CompositeWPF (Prism) Applications

Version: 1.0
Description: Article about the OutlookBar for Composite WPF applications.

Customizing regions in CompositeWPF

Version: 1.0
Description: Article about how to customize regions in Composite Application Guidance for WPF by using databinding.

Creating closeable tabitems for use in CompositeWPF

Version: 1.0
Description: Blog post on how to create closeable tabitems.

Updated Wiki: Composite Application Guidance for WPF

ibaumann — Fri, 10 Oct 2008 15:11:45 GMT

Composite Application Guidance for WPF

Patterns For Building Composite Applications With WPF

Version: 1.0
Description: This article discusses Composite Application basics, Bootstrapper and Module Initialization, Regions and RegionManager, Views, Commands and Events.

Prism: Composite WPF Guidance

Version: 1.0
Description: Composite Application Guidance for WPF overview.

Prism vs Framework XXX

Version: 1.0
Description: Prism development & out of the box characteristics.

RegionManager Question

Version: 1.0
Description: Question on RegionManagers.

IModuleEnumerator guidance

Version: 1.0
Description: Information on module enumeration.

DirectoryLookupModuleEnumerator Child AppDomain

Version: 1.0
Description: Information on why a child AppDomain is created in DirectoryLookupModuleEnumerator.EnsureModulesDiscovered.

Updated Wiki: GettingStarted

ibaumann — Fri, 10 Oct 2008 15:10:47 GMT

Getting Started

Prism 2.0 - First Drop

Version: 2.0
Description: Article describing the new features of the first drop of Prism 2.0. This new drop is focused solely on the "multi-targeting" aspects of Prism. Multi-targeting is the ability to build applications that can provide both a WPF desktop and a Silverlight RIA experience by sharing and re-using code and components between the WPF and Silverlight environments.

Use case controllers, container hierarchies and services in composite WPF

Version: 1.0
Description: A summary of use case controllers, container hierarchies and services in composite WPF.

Getting Started with the Composite Application Guidance for WPF

Version: 1.0
Description: Article with overview about what is Composite Application Guidance for WPF.

Composite Application Guidance for WPF (Prism) Tour - Part 1

Version: 1.0
Description: Article with overview about what is Composite Application Guidance for WPF and why or when is necessary. (Part 1)

Composite Application Guidance for WPF

Version: 1.0
Description: Article about the features of the Composite Application Guidance for WPF.

New Post: ERP in Composite Library

guptapv — Fri, 10 Oct 2008 09:59:48 GMT

Hi,$0Thanks for encouraging words and its a great sense of relief as I am really looking forward to go for composite.$0$0$0$0$0Let me go bit specific to issues which I am facing.Actually I am infact looking to build a product over this order in large run and it should be configurable.$0$0Based on my experiance and interection with ERP users,we need following things in place ...$0$01.Gone are the days for MDI .$0$02.User should have flexibility to open multiple windows at a time.$0$03.All forms wherever relevant should have shortcuts to open.e.g. User should have facility to create new customers from quotation itself or wherever cutomer selection take place.It goes true for all such scenarios.$0$04.Large forms ,say for customer master should have capability to have entry form open with selective views e.g. if I want to alter his payment terms or say address or may be financial info,full for should not get loaded and user should have the flexibility to choose how much he is willing to have on form.Now in contrast some user would always love to have everthing in single form.Thats where composite appeals me most but not sure if it can match to my requirment.$0$05.Matching to previous point is also the facility to restict views according to user rights.$0$06.Workflow and change request should againt be available at unit leven and it should be optional.Say a user has prepared a quotation and higher authoirty freezed rest of the document but want to intimate user to change only payment terms.$0$0$0$0$0Please provide your views if composite will not restrict me to do all this and if some examples are availeable in this regard.$0$0$0$0$0thanks....$0

New Post: ERP in Composite Library

kumartan — Fri, 10 Oct 2008 07:05:34 GMT

I have gone through Same kind of ERP project (Complex business logic and user interface interaction )before 2 years and we choused CAB/SCSF. I feel composite WPF is very much street forward technology then CAB/SCSF and mature enough to deal with complex business logic. Based on my experience with CAB and knowledge about Composite WPF, no doubt your choice is right. Don’t worries go-ahead. Because your problem is very generic, we could really work together if you come up with some user story.

New Post: ERP in Composite Library

guptapv — Fri, 10 Oct 2008 06:40:53 GMT

Hi,$0I have got a erp project which includes all essentail modules like sales,procurment,CRM,Finance etc and WPF has been decided as front end.I found concept of composite library very interesting but not able to decide if it is good enough to handle requirments of complex user interection which is must for ERP kind of application and is it matured enough to go for it.Also sample and applicatios provided with it does'nt give me full confidence to go for it.I am interested in knowing if some of the people are really upto the complex application with composite liabrary and if possible would need some guidenace and their experiances.$0$0I am feeling strongly for it but not getting enough confidence to go for it.$0$0Any help would be highly appericiable as its a big decision for me .$0$0$0$0

New Post: Resolve Problems

findjammer — Thu, 09 Oct 2008 20:45:56 GMT

Ahh ... schoolboy error ...

I was registering my ExportPage at module initialisation BEFORE registering the type detailed above hence ... two instances kicking around ... DOH! (>_<)!!

New Post: Resolve Problems

findjammer — Thu, 09 Oct 2008 20:35:27 GMT

Hi All,

I'm having a resolve problem that I'm struggling with at the moment, any pointers would be great.

At the initialisation of ModuleA I register a Type like:

_container.RegisterType<IExportViewDataModel, ExportViewDataModel>(new ContainerControlledLifetimeManager());

I was under the impression this was almost like registering a Singleton?

In the same Module I need an instance of ExportViewDataModel which I get from the the container by:

this._dataModel = _container.Resolve<ExportViewDataModel>();

Now in ModuleB I also need a reference to the same instance of ExportViewDataModel which I get from the container by:

this._exportViewDataModel = _container.Resolve<IExportViewDataModel>();

However, I'm seeing the ExportViewDataModel constructor being called twice which means anything accessing the IExportViewDataModel is pushing data into one instance and the ExportViewController is pushing data into another instance of the ExportViewDataModel. I'm really confused by this as I was under the impression that since the type is registered with the container using the LifetimeManager that I would always be provided with a reference to the same instance.

Any help, ideas would be great.

Thanks,

James.

New Post: Outlook style regions

iwhp1 — Thu, 09 Oct 2008 17:07:55 GMT

I came up with the following.
On all Views I have a interface defined (IView). This interface makes sure that all views have a property called "Visibility".

IView.cs
    public interface IView
    {
        Visibility Visibility { get; set; }
    }

XxxxView.cs
        Visibility Visibility
        {
            get { return this.Visibility; }
            set { this.Visibility = value; }
        }

I am not sure if I should have used another name for the property, or how to make the underlying "this.Visibility" availalbe public.
Anyway, I now have the possiblity to hidde, collapse or make the view visible.

            foreach (object item in new List<object>(this.regionManager.Regions["ListRegion"].Views))
            {
                ((IView)item).Visibility = Visibility.Collapsed;
            }
            view.Visibility = Visibility.Visible;

Cheers Harry

New Post: common XAML approach in Prism

emj — Thu, 09 Oct 2008 16:52:26 GMT

Julian,

Thanks for replying. Looks like it makes more sense to have them separated. Do you think that will change in the future?

Thanks,
Eric