I'm learning Expression Blend / XAML / WPF etc. for a new .NET application design project. The tool (and WPF underneath) is large and baffling, but I'm not too worried about that. Practice time will help me grow more proficient, and I'm decent with C# and XML. I've got a great developer to partner with.
What I would really like to know more about though comes in at a bit higher level. I'd like to know more about what works (or not) in a Blend project. Those of you with Blend experience... - Is there something you built the first time, and then tore out and rebuilt differently? What was it, and why? - Is there an architecture that seems to work well for you to integrate many different pieces of a large and complex application? - Can you describe a bit of the workflow process between yourself and your developers? Did your developers create objects first, and then you tie into them, or the other way around? - Are there any design practices that have seemed particularly effective when working with a Blend project? - Any great 3rd-party control sets you'd recommend? - Any advice you wished someone had given you when you were a Blend newbie? Very grateful for any advice you can share. Thanks also to Chris B and David M for previous helpful threads and comments. Michael Micheletti ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
