Appropriate pattern

[Mike]

Hi,

I have 4 user controls that are used in a wizard form. Since I also wanted
to re-use those controls when editing the same information that are created
with the wizard. I used a class (Facade pattern) to ease the interaction
with 4 user controls. The problem is that each of the user controls also
contain information that are used in a business object, which I cannot
access directly.

I was thinking about the Mediator pattern to get all the various properties
contained in the various user controls in a "central" place and then set up
getters to retrieve this information in the Facade class. I want to avoid
building a too complex system. What are your thoughts?

Thanks.
Mike

 

[Gabriel Lozano-Morán]

To clearly understand the problem, are you saying that the business object
needs information from the user controls or the other way around? And the
interface of this business object won't change?

Anyway my first impressions is more like a MVC like approach where the
business object is the model and the user control(s) the view(s) instead of
adding the complexitiy of a Mediator.

Gabriel Lozano-Morán
The .NET Aficionado
http://www.pointerx.net

 

[Mike]

Yes, the user controls need information from the business object and the BO
needs information from the user controls (basically, when loading data, the
UC gets data from the BO, and when saving data, teh opposite occurs).

I see what you with the MVC.

Thanks.
Mike

 

[Dave Sexton]

Hi Mike,

Wizards are commonly written using User Process Components. Microsoft has
an application block to help:

"User Interface Process Application Block for .NET"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/uip.asp

 

[Dave Sexton]

Hi Mike,

I see that I posted an older link before, sorry. Here's the latest:

"User Interface Process (UIP) Application Block - Version 2.0"
http://msdn2.microsoft.com/en-us/library/ms979217.aspx