views:

86

answers:

2

This was inspired by a question I asked recently regarding design time behaviour in my WPF app. (http://stackoverflow.com/questions/2290499/cant-databind-at-design-time-in-wpf-using-mvvm-viewmodel-property-never-gets-c)

The net result of that is that my design time DataContext/ViewModel works perfectly in Blend, but doesn't show up in Visual Studio 2008. I've decided not to look further into it as Blend support is all I really need, but this surprised me as I had been working under the assumption that Blend and VS would have similar if not identical WPF designers.

So what are the differences? Any other gotchas anyone is aware of? All info welcomed :)

+1  A: 

In short, WPF matured after VS 2008, so the designer is pretty much crap since it went in very late in the development cycle for Visual Studio.

In VS 2010 however, the designer is much improved (as well as app WPF stuff in general...a lot of the VS 2010 components are WPF themselves), but I would stick with Blend for now. I personally use Blend for the design, Visual Studio for the code.

Coming up shortly with VS 2010/WPF 4:

Nick Craver
Thanks Nick. As I updated above I'm hoping for some real info on what's happening behind the scenes, but in the quite likely event that that never surfaces this is a perfectly good answer and at least explains why Blend does what I expect while VS 2008 doesn't. I'll accept this if no more detail pops up as it's good info :)
randomsequence
A: 

hi dude, i just want to tell what's my opinion. In Visual Studio 2008 and Visual Web Developer 2008, both don't have the function of designing UI. so your design doesn't show in VS2008. but In Visual Studio 2010, it becomes better.Visual Studio 2010 will support a fully editable and interactive designer for Silverlight.

kiddy