Don't worry too much about eliminating code behinds.
Carl, I have decided that having empty code-behind is an academic exercise in elegance that will waste a lot of my time. My policy from today on in SL and WPF is to minimise the code-behind, but only up to the point of "comfortable effort". I have a couple of places where child controls are dynamically loaded, try that without code-behind! Making my controls "Blendable" with mock data is not so important, it's more vital that my controllers be unit testable, and my currently model is okay in that respect. At some point I know things will start to make more sense for you. Everything does make sense (generally), I'm using quite advanced techniques in this SL project, it's just that SL is full of holes and workarounds (ICommand, dynamic styling, globalization for example) and there are too many conflicting tools, articles and sample code. Over the last week I've seen 3 wildly different ways of implementing ICommand and attached properties, and a lot of my time was wasted evaluating them all. I struggle with catastrophic errors, security stonewalls, WCF behaviour complexity, Blend and VS2008 XAML designer failures and assembly bloat, all of which I'd expect in a beta product (is the beta period over yet?). Cheers, Greg Ps. Carl, can you darken your font a bit ;-)
_______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
