WCSF vNext – What’s important to you?


As Blaine menioned, we’re right at the point when we are about to begin planning for the next version of WCSF. I’d like to hear what you think we should be building. In the spirit of Tom’s prior post, let’s use the monetary system. You’ve got $100 to spend on building WCSF. What features would you include, and how much would you spend on each? (in terms of importance to the release). Let your mind loose concenring features, and don’t be afraid to ask us to invest in restructuring / refactoring to make the factory more friendly / usable.


Here’s a few ideas to get things rolling. Some of these are based on the most voted upon in the issue tracker. Others are ideas I am throwing into the mix based on gut feelings and customer exchanges. Feel free to add additional items not on this list.



  • Entlib 3.0 support (VAB, PIAB), etc
  • ASP.NET AJAX Support
  • Silverlight [WPF/E] Support
  • Complex Page Flows
  • UI Composablity
  • Less manual coding, more configuration, i.e. Service Registration via config, etc.
  • Making the factory model driven. (Supports adding, removing and editing existing artifacts)
  • Visual tools for navigating the factory solution projects and class files.
  • Code snippets for repetitive tasks
  • Richer debugging i.e. visual tools.
  • Performance enhancements

OK, on your mark, get set, GO!


 


Technorati tags: , ,

Comments (19)

  1. tomholl says:

    I presume this is in Australian dollars, just like for the EntLib prioritization? 😉

    Tom

  2. gblock says:

    I am speechless

  3. Adrian says:

    Entlib 3.0 support (VAB, PIAB), etc 20$

    ASP.NET AJAX Support  20$

    Silverlight [WPF/E] Support 20$

    Complex Page Flows 5$

    UI Composablity 5$

    Less manual coding, more configuration, i.e. Service Registration via config, etc. 5$

    Making the factory model driven. (Supports adding, removing and editing existing artifacts) 10$

    Visual tools for navigating the factory solution projects and class files. 10$

    Code snippets for repetitive tasks

    Richer debugging i.e. visual tools.

    Performance enhancements 5$

  4. Eric Schatzschneider says:

    Entlib 3.0 support (VAB, PIAB), etc – $20

    ASP.NET AJAX Support – $10

    Silverlight [WPF/E] Support – $10

    Complex Page Flows – $15

    UI Composablity – $10

    Less manual coding, more configuration, i.e. Service Registration via config, etc. – $10

    Making the factory model driven. (Supports adding, removing and editing existing artifacts) – $15

    Visual tools for navigating the factory solution projects and class files. – $5

    Code snippets for repetitive tasks – $0

    Richer debugging i.e. visual tools. – $0

    Performance enhancements – $5

  5. Eric Schatzschneider says:

    I want to modify my above choices with the following changes:

    ASP.NET AJAX Support – $8

    Silverlight [WPF/E] Support – $7

    UI Composablity – $15

    After doing a bit more research I released that UI Composablity was more important then I originally thought.

  6. Kevin Bond says:

    $20 Entlib 3.0 support (VAB, PIAB), etc

    $30 ASP.NET AJAX Support

    $0 Silverlight [WPF/E] Support

    $20 Complex Page Flows

    $10 UI Composablity

    $10 Less manual coding, more configuration, i.e. Service Registration via config, etc.

    $0 Making the factory model driven. (Supports adding, removing and editing existing artifacts)

    $0 Visual tools for navigating the factory solution projects and class files.

    $5 Code snippets for repetitive tasks

    $0 Richer debugging i.e. visual tools.

    $5 Performance enhancements

  7. Vaithees says:

    Hi

    Glenn glad you are in here.

    Spend all the possible dollars.  Provide page flow customization

  8. Ralf says:

    $20 Entlib 3.0 support (VAB, PIAB), etc

    $40 ASP.NET AJAX Support

    $0 Silverlight [WPF/E] Support

    $10 Complex Page Flows

    $30 UI Composablity

    $0 Less manual coding, more configuration, i.e. Service Registration via config, etc.

    $0 Making the factory model driven. (Supports adding, removing and editing existing artifacts)

    $0 Visual tools for navigating the factory solution projects and class files.

    $0 Code snippets for repetitive tasks

    $0 Richer debugging i.e. visual tools.

    $0 Performance enhancements

  9. Patrick Yong says:

    $50 VB.NET and C# Concurrent release

    $30 Entlib 3.0 Support

    $20 UI Composablity

  10. Leonid Shirmanov says:

    $50 for Entlib 3.0 support (VAB, PIAB) because it’s blocking feature

    $20 Code snippets for repetitive tasks

    $15 Silverlight [WPF/E] Support

  11. Roy Higgs says:

    $20 Entlib 3.0 support (VAB, PIAB), etc

    $20 ASP.NET AJAX Support

    $0 Silverlight [WPF/E] Support

    $10 Complex Page Flows

    $20 UI Composablity

    $5 Less manual coding, more configuration, i.e. Service Registration via config, etc.

    $5 Making the factory model driven. (Supports adding, removing and editing existing artifacts)

    $0 Visual tools for navigating the factory solution projects and class files.

    $5 Code snippets for repetitive tasks

    $0 Richer debugging i.e. visual tools.

    $10 Performance enhancements

    $50 WCSF Configuration Validation – still can’t create business/foundational modules after upgrading an existing web site project. Would be nice to be able to run a tool to validate the configuration in the sln and config files.

  12. OK, I am about to take a community leap of faith. There’s been several discussions going on on the web

  13. Alain says:

    Webpart : Ability to create webpart from user control at runtime.

    Can be implamented as an attibute put on usercontrol class.  Can be cool to have Webpart catalog discover our usercontrol (ascx/dll) at runtime.

  14. Paolo says:

    I would love to see the event broker from SCSF ported to WCSF or a new one built. I love the composability of the eventing system.

  15. Marty Bell says:

    Hey Glenn….it’s taken a while but here’s what we would like to see…..

    1) Guidance on building a custom page flow provider

    2) More complex usage scenarios….the feeling is the samples are not reflective of real world scenarios

    3) Tooling to customise the recipes and templates

    4) Undo recipes….if we change our mind it’s quite hard to undo what certain recipes do

    5) More stable recipes….when they bomb it can leave VS fairly unstable….the main culprit seems to be creating test projects

    6) The ability to build the site map from registered modules without hard-coding URLs into the module initialiser

    Cheers

    Marty

  16. Art says:

    Entlib 3.0 support (VAB, PIAB), etc – 20$

    ASP.NET AJAX Support – 25$

    Silverlight [WPF/E] Support – 20$

    Complex Page Flows – 20$

    UI Composablity – 5$

    Less manual coding, more configuration, i.e. Service Registration via config, etc.

    Making the factory model driven. (Supports adding, removing and editing existing artifacts)

    Visual tools for navigating the factory solution projects and class files.

    Code snippets for repetitive tasks

    Richer debugging i.e. visual tools.

    Performance enhancements – 10$

    and Im agree with point:

    2) More complex usage scenarios….the feeling is the samples are not reflective of real world scenarios

  17. Santiago says:

    $10 Entlib 3.0 support (VAB, PIAB), etc

    $30 ASP.NET AJAX Support

    $10 Silverlight [WPF/E] Support

    $10 Complex Page Flows

    $10 UI Composablity

    $0 Less manual coding, more configuration, i.e. Service Registration via config, etc.

    $10 Making the factory model driven. (Supports adding, removing and editing existing artifacts)

    $0 Visual tools for navigating the factory solution projects and class files.

    $5 Code snippets for repetitive tasks

    $10 Richer debugging i.e. visual tools.

    $5 Performance enhancements

  18. The last 24 hrs have been a blogothon of queued overdue posts, this one is LONG overdue. With the recent

  19. The last 24 hrs have been a blogothon of queued overdue posts, this one is LONG overdue. With the recent