Leave a Reply


  1. Something that will really change your way of programming a client is the way SL more or less forcces you to program asynchronously. It’s not just that you have to subscribe to lots of Completed events, it’s also the way you lock the UI to prevent multi-triggering the job that you are waiting for (e.g. prevent a order to be ordered twice)

    Be carefull with using opacity 0 for the WPF-Hidden. It is not the same. WPF-Hidden causes the control to be skipped while rendering; I am not sure whether SL will render the zero opacity control. It might look the same but it might be slower.

    LOB’s are on their way! Read about the RIA Service Framework here: http://go.microsoft.com/fwlink/?linkID=144687 or even download it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=76bb3a07-3846-4564-b0c3-27972bcaabce

    BTW: some of your annoyances will be solved with version 3 (more 3D and element to element binding)

    Erno de Weerd Reply

  2. Erno thanks for the extra info! Obviously there still is a lot to discover for me in SL development.
    The zero-opacity vs. hidden is something interesting to dive into. Sometimes you just want to hide an element but still let it use some space (should prevent layout changes when the ‘functional visibility’ is toggled). Maybe I’ll get back to that. 🙂

    josd Reply

  3. Actually the ResourceDictionary is there. The only thing that is missing is the possibility to create a merged resource dictionary.

    Currently I’m working together with a few colleagues on a LOB application and we’re making good progress even with the in my opinion small irritations.

    One of the things we are tackeling at the moment is validation of data entered in the user interface with the limited infrastructure of silverlight. It’s a challenge, but we’re getting there 😉

    willemm Reply