Windows Workflow Foundation design limitations
I've been trying lately to customize some WWF components and activities to fit my needs. In many cases I find that mostnice classes are sealed for no good reason!!
For example, say you want to customize the PolicyActivity to add some new property or even simpler change its appearance. You have to find another way to do that, but you cannot inherit.
Also many helper classes are internal and the some good functions that might help customizing are marked internal. As an example, the good looking curved connectors in the state machine diagram, they are marked as internal.
Now all this is put constraints and make developers life harder when trying to extend already existing object model in WWF.
Any one can give thoughts for why such design decision was taken!! Any thoughts? I'm just trying to share thoughts and experience.
