Design-Time data and ViewModel first. Is there a convenient solution?

Nov 5, 2010 at 12:16 PM


Anybody knows a way to have a good enough design-time data support when using Caliburn.Micro, particularly with ViewModel first approach?

There is d:DataContext, it works well in some cases. But it's failing when views are using CM's convention system. You have to state explicit your bindings to get design time.

I've seen few implementations and recommendations in other mvvm/ui frameworks, for design-time, but haven't decided which way to take: separate datacontext, another service layer and so on... Not really preferred neither, and they are not handling conventions.

Can Caliburn.Micro offer something clever here? Somebody has a recipe for design-time data?