Some of you are spot-on regarding some of your nits around Expression (simplification of the true story, lack of TFS integration, …) The short answer for TFS is that we’re really looking into it. You wouldn’t guess this by looking at the results, but the Blend team is really small and hence, picking TFS support over other stuff becomes a very tough prioritization exercise – enable tooling parity for Silverlight 2.0 or TFS or one of a thousand other feature requests? It’s a tough call, and I’m happy I don’t have to make it (but I do occasionally throw fuel at the fire for the same reason internally. It’s too easy). I won’t delve into each of the points made, but suffice to say that I agree with a lot of the issues you raised and so do folks on the teams. They’re working on it.
“Aren't we just getting the same tired "designer/developer separation" scenario to sell the Expression/Visual Studio products that was being over-sold at the first MIX two years ago? We should have moved on by now, and yet the same old overly-simplistic platitudes are being spouted out as if everything was there today.”
We could do a better job across the board as we talk about the progress being made to enable a better workflow amongst folks who build web sites and web apps. Agreed. But let’s not stop talking about solving the core problem of fixing the workflow. It’s a tough nut to crack and it is what makes me wake up every morning. The real message that often gets lost in translation is this – Expression Studio is built on the core philosophy that the workflow between folks creating web sites, RIAs and applications is broken and that’s what the tools and the platform are striving to fix. Are we there yet? No. But, it’s a fantastic start, especially for a v1.
I could go into some of the comments about designers and MIX, but I’m going to save that for another day. That stuff is close to my heart, and I have lots of opinions in that area.
Great comments in this thread. Thanks for the feedback and conversation.
User Experience Evangelist