Advertisement

POLL: Silverlight developer patterns

My friend Joel Neubeck is doing a survey on his site about what patterns people prefer for Silverlight development.  I’m very interested in these results as well, so if you have 2 seconds, please post your vote:

Link: Poll: What separation pattern do you prefer in Silverlight development?


This work is licensed under a Creative Commons Attribution By license.

  1. 2/10/2009 2:58 PM | # re: POLL: Silverlight developer patterns
    I don't know enough about them, but I'm waiting for one of your videos to learn specially the M V V M pattern in silverlight.
    Thanks again for the good work.
  2. 2/10/2009 3:21 PM | # re: POLL: Silverlight developer patterns
    Separation of concerns and Dependency Injection are both very valuable in applications. When I explain patterns to people I throw out the terms and talk about what makes sense to developers ... things like having developers work on separate parts of the project and hooking together without running into each other. Also, being able to deploy parts of an application at a time instead of the app as a whole. Being able to design the UI with a designer and have the coding done separately ... with no close to 0 code in the codebehind. Too often we get into patterns and we lose sight of why we are using them. Adoption would be greater if people could grasp why they are important, IMO.

    Standards for patterns are a hurdle too. There is no place to go to see how to correctly do MVVM in Silverlight, for example. Guys like me will post our own flavors of it, but int he end its subjective.

    My point is that MVVM is a solid pattern and it works quite well for Silverlight. We need to come up with some solid techniques for explaining MVVM in Silverlight, teaching it (videos/tutorials/samples/etc), and evolving with it.

    Prism is a good starting point.
  3. 2/10/2009 4:42 PM | # re: POLL: Silverlight developer patterns
    I would like to hear the difference between MVVM MVC and MVP as they pertain to silverlight. The examples I have seen of MVVM create a View Model to do mapping between data like int's and colors, so the View Model becomes a way to extend the O-R mapping class. Which begs the question, why not use partial classes to create the View Model?

    Also should fact the Silverlight runs on the client, and not the server, make one pattern better that another?
  4. 2/10/2009 10:14 PM | # re: POLL: Silverlight developer patterns
    @Rachida Dukes
    Check this blog: http://blog.lab49.com/archives/2650

    @steve Strong
    - no physical dependency between view and model
    - model can be unit-tested
    - a Silverlight model may can be used for a WPF client
  5. 2/11/2009 9:08 AM | # re: POLL: Silverlight developer patterns
    Thanks for the link, I'm definitely interested to look at it.
    Thanks again
    Rachida
  6. 2/12/2009 12:40 PM | # re: POLL: Silverlight developer patterns
    The most recent issue of MDSN magazine has a super excellent article on the MVVM, with good code examples. It is quite understandable. Don't miss this one!

 
Please add 2 and 4 and type the answer here:
First time here? You are looking at the most recent posts. You may also want to check out older archives. Please leave a comment, ask a question and consider subscribing to the latest posts via RSS or email. Thank you for visiting! (hide this)