Why arent Expression Products Available on MSDN?

It's still a valid issue to be raising.

I think the distinction between these and development tools is spurious and artificial.

Additionally, I think that rather than repeating or implicitly promoting  a lot of clichéd ideas about the differences between developers and designers (and the inherent colour-blindness, style-bindness and lack of artistic sensitivity of the former), we should maybe, just maybe explore the possibility that in some people's case the difference is not actually at DNA level, but is simply a consequence of what they have or haven't learned.

In that spirit it would be good to provide a set of developer-oriented design resources (I mean of an educational/guidance nature) to help developers get their heads around design tools and principles and maybe decide whether that's an area they'd like to seek training in.

This is not just because I loathe developer stereotyping (by Microsoft, the media, and for that matter developers themselves), but also because no matter how good the design tools are, I strongly suspect the Microsoft world is going to have a hard time deprogramming enough Mac-cultist designers (yes I know, I'm stereotyping, but tell me there's no truth in it) to provide the UI skills we need. I still shudder when I remember interviewing people for a web designer position, and watching them all recoil at the notion of even touching something that would eventually be used on a Windows machine.

So re-tooling other people to at least start them on the road to being useful in that area seems like a good idea.

Sorry for straying off-topic...so to return to the point: The Expression toos should be included in MSDN subscriptions. So come on Microsoft - no spin, no lame excuses, no marketing-cum-manager-speak. Just fix it.