Roadmap for WCSF

A number of customers have asked about the future of the Web Client Software Factory. I want to announce that we are starting to plan for the next release of the Web Client Software Factory. We plan to start the project in the spring of 2009 and plan to deliver this next version with Visual Studio 2010. I need your feedback as to the scope for this next release. The overall process for this release is the following.

  1. Announce intent for release and ask for scope requests

  2. Obtain feedback from you and other customers to create candidate scope list

  3. Publish survey to prioritize candidate scope

  4. Build vision/scope from prioritized scope

  5. Start project & deliver the project (if only it were this easy 

We will take feedback from the following sources for the release:

  • Obtain feedback from my blog and Michael Puleio's blog

  • Obtain feedback from

  • Obtain feedback from advisory board

  • Obtain feedback from direct customer discussions

  • We are considering a number of new features for Web Client Software Factory. This list is to get the discussion started but it will not be the final scope which is why we need your feedback. We will not have time to implement all of these features and I am confident that you will provide many other ideas that are not on the list.

    List to start the discussion:

    • Unity for a container

    • Composite support for MVC

    • Support for Web pages through dynamic data

    • Eliminate the use of a base class similar to what we did for Prism

    • Allow library to be pluggable so you can use your own components including the container

    • Support for Silverlight controls on your Web pages

    • Allow Web Client Software Factory controls to be reused with SharePoint

    • How to distribute logic between layers of the architecture

    • Improve performance of CWAB

    I need your feedback on what you think we should focus on. I also need your help to build a list of customers that are using the Web Client Software Factory. I constantly have customers that are asking who else is using it. Additionally it is helpful to have this list to put the business case together for how much budget we should spend on this next release. So please help me build my list of customers.

    As for support, we will continue to provide support for WCSF through our Codeplex site.


    Comments (10)

    1. First new and notable with the new Graffiti blog. WCF/Cloud Services Aaron has his latest in his series of WCF screencasts , this time showing how to host WCF services within traditional Windows services Aaron also has a geekSpeak webcast on Cloud Services

    2. Blaine & I have been getting a lot of emails, messages, comments, etc about WCSF.  There are

    3. Have you been using the Web Client Software Factory ? Or have you tried it and not adopted it? Or have

    4. Para los amigos que me han estado preguntando sobre el futuro del web client software factory (WCSF)

    5. jkinter says:


      We were using WCSF for some things, but have moved to Silverlight for web content because it allows us to use a common shared-library codebase. We are very interested in WCSF’s future because we would like to have a truly "thin" client solution. To be honest, we’ve moved all of our development toward a scenario where web-apps can be developed using Silverlight, Prism and MEF and thick clients can be developed using CompositeWPF, Prism, and MEF and deployed using ClickOnce. The only reason we’re not wringing our hands over the architectural disparity between WCSF and CompositeWPF is that we typically develop Intranet applications and have control of the destination machine. This makes Silverlight particularly appealing. We try to develop LOB apps that can be reused across projects..for example, an app that is developed to manage employee information will be built so that the interface can be abstract and then the "employee" component can be reused in any other LOB application that needs to interact with an "employee". In this example, one LOB application may have a "thick client" user interface requirements, while another [tangential] application may have a "thn-client" user interface requirement. Currently, we’re satisfying the latter by developing for Silverlight 2. Someday, we expect that we will need to have a "thinner client [i.e. web]" requirement and we would hope that one day we would be able to target WCSF, Unity, and MEF for this….and in particular, the ability to host the WCSF "app" in a SharePoint friendly/aware way.


    6. says:

      I would find it helpful for there to be an interim release delivered as soon as possible whose only feature would be to replace ObjectBuilder with Unity.



    7. philosophil says:

      Personally, I’d like the next version to:

      • work with 2010
      • work with Unity

      • work with the latest version of EntLib

      • work with sharepoint

      Not on your list:

      • auto data bubbling

      Suppose I have a page that knows that you should display product X, then all child controls that need product X should be able to access it fully initialized and ready to use.

      The above is kind of easy, it gets tricky when you deal with repeaters and list of items.

      In short it’s dependency injection but for data and not just run-time components.

      Thanks for the good work by the way.

    8. A number of customers have asked about our plans for the Web Client Software Factory and the Smart Client

    Skip to main content