There is a nice article from Karsten Januszewski called Hitting the Curve: On WPF and Productivity you might find interesting:
Let's be clear: WPF comes with a
curve. I've now watched a bunch of
developers hit that curve. And the
curve is steep. We're talking between
two weeks to two months of curve
depending on the developer and the
level of experience/intuition the
developer has. There will be moments
of total mystification and plenty of
moments of illumination. It is at once
painful and enjoyable, if the
developer delights in the discovery of
a deep and well thought out UI
platform. It is at once familiar and
alien. There are many similarities to
other UI development paradigms: styles
feel like CSS, well sort of. XAML
code behind feels like ASP.NET, well
sort of. 3D feels like DX or OpenGL,
well sort of. Routed events feel like
.NET events, well sort of. Dependent
properties feel like properties, well
sort of. The list could go on. But
admidst these (sort of) familiar
metaphors there are so many alien
concepts that must be mastered:
control templating, storyboards,
databinding come to mind immediately.
It is not a trivial curve and don't
expect to be productive on day 1 or
even week 1 or even month 1.
It's all worth it though! ;)
