CAB, SCSF and Application blocks RRS feed

  • Question

  • Is there any sense of the following technologies falling out of favour since the arrival of WPF.




    User interface Application block

    Asynchronous Invocation application block


    I'm wondering if the architectural patterns that form the basis for some of these technologies have been superseded somehow?


    Any thoughts.


    Saturday, March 15, 2008 10:21 PM



    The frameworks you are citing here are all from p&p. Their motto is to make things with what it's available today filling the gaps left by product teams. However, they are not a product team, so there is a chance that they do not keep putting efforts on those libraries/frameworks.


    Said that, WPF is certainly not there yet for LOB apps and the patterns you will find in CAB/SCSF are not yet part of WPF. That's why p&p is working on something called Prism (http://blogs.msdn.com/gblock/archive/2008/03/12/prism-ri-first-drop.aspx) and that's why we wrote the WPF layer of CAB in SCSF Contrib (http://www.codeplex.com/scsfcontrib).

    I believe in the patterns you can find in CAB and I don't think WPF is superseeding them. They are orthogonal in my opinion (except for the Command pattern that is present in both CAB and WPF). WPF brings to the table something Winforms does not have which is the visual richness. This will lead into apps we had not been doing before, but the patterns (composition, MVP, plugin, DI, Service Locator, Event Pub/Sub) will remain very similar.


    Glenn is the Product Manager of the client team at p&p. You will find in his blogs some of this rationale





    Sunday, March 16, 2008 8:51 PM