Scope for Prism 2.0


In my previous post, I mentioned that we planned on creating guidance for Composite Silverlight applications. David Hill just blogged on our plans for Prism 2.0. From this survey we heard you wanted guidance on:

  • Multi-targeting controller, presenters, services, and models for both Silverlight and WPF
  • UI Composition for Silverlight
  • Modular Development for Silverlight
  • Data access

Based upon this feedback we decided to create guidance that will help you create Multi-targeted Silverlight and WPF applications and Composite Silverlight applications. We plan to use the existing Prism…I mean Composite Application Guidance for WPF as the starting point.

Based upon your feedback, we decided to guidance on SharePoint Intranet Development. This includes help with solution architecture, solution development, and packaging and deployment.

Elevator Pitch:

Target Customer: Primary: Silverlight Professional Developers (Includes Architects); Secondary: Human Designer

Statement of Need: Build new multi-targeted Silverlight and WPF client applications maintained by multiple teams (composite application).

Product Name and Capability:

  • Prism…Composite Application Guidance for Silverlight 
  • Reusable components, guidance, automation and samples for developing composite WPF and Silverlight applications
  • Enable cross-targeting of applications for WPF and Silverlight easier.

Key Benefit:

  • Provides infrastructure for developing and maintaining WPF and Silverlight composite applications
  • User Interface components are dynamically composed
  • Application modules are developed, tested and deployed by separate teams
  • Allows reusable components across WPF and Silverlight applications
Focus Areas of the Guidance:

Multi-targeting:

  • Developer needs to reuse controllers, presenters, services, and models across Silverlight and WPF: Must Have
  • Developer needs reuse unit tests across Silverlight and WPF: Delighter
  • Developer needs to reuse validation across Silverlight and WPF: Delighter
  • Developer needs reuse UI elements across Silverlight and WPF (styling to views): Delighter

Composite Application Guidance for Silverlight

  • Developer needs guidance on creating a Composite User Interface for Silverlight: Must Have
  • Developer needs guidance on creating modular application for Silverlight: Must Have

Line of Business Guidance for Silverlight

  • Developer needs guidance on how to query data and send updates to the server: Delighter
  • Developer needs guidance on how to create validation rules: Delighter
  • Developer needs guidance on how to authenticate and authorize users: Delighter
  • Developer needs guidance on how to cache data on the client: Delighter
  • Developer needs guidance on logging and exception handling: Delighter

Note that the Must Have’s we plan on addressing. The Delighter’s we will complete as many as we have time which of course could be none. Give us your feedback on the scope. Are we tackling the right set of challenges?

As an fyi, David Hill recently joined the p&p team and we are really happy to have him on board. I have had the opportunity to work with David in many different roles over the last 5 years. David played an advisor for some of our early Smart Client work which included the Offline Application Block and CAB. He also helped us write the Smart Client Architecture and Design Guide. More recently David was an advisor from the product team for Prism 1.0 and played a big role in helping us simplify the experience of adopting Prism. We are glad that he will be “pig” on Prism 2.0 for those that understand the pig and chicken analogy from SCRUM.

Comments (8)

  1. adam.hill@gmail.com says:

    What about "The Porter"?

    More often than not you will get an "X" (where X is an App or a Control) and be asked to port it over to "Y" (where Y is Silverlight or WPF).

    It would be nice to have a list of "Things that Will Make Your Life Hard" and "Things That Will Make Your Control Non-Portable" when coming from either direction. And some Guidance from MS about things you will have to give up when porting in either direction.

    Because now there exists the possiblilty for certain apps to cross the RIA divide and emerge unscathed"

  2. Blaine says:

    Adam,

    Thanks for the feedback. We will have some guidance on how to make your code work on both Silverlight and WPF (multi-targeting).

    We are not currently planning to create guidance on porting from one to the other. If we get lots of feedback that this is more important than other items on the list, we determine how we can provide guidance to address he request.

  3.    So known Prism project is making some changes on the spectrum of WPF Applications, with

  4.    So known Prism project is making some changes on the spectrum of WPF Applications, with

  5. Brad Abrams says:

    I’d love to hear feedback and thoughts you have about building business focused applications with Silverlight. 

  6. We just finished our first drop for Prism 2.0 and posted it on Codeplex . As previously announced , we

  7. Programming says:

    I'd love to hear feedback and thoughts you have about building business focused applications with

Skip to main content