Now we're cooking. 4 it is.

Typically said after I have looked down the road and proposed a feature that I think is really critical but is seen as time consuming, which it usually isn't. "Let's make that a version 2 feature" = "I think that's a waste of time, or I don't understand it so I'm not going to buy in to it." Um, and I just deployed version 3.5.1, so if you are going to shrug off my suggestions and try to make it look like you are in any way release-planning, at least act like you are planning an actual release. :mad:

Hey Gigs... Start here: WPF/MVVM Quick Start Tutorial[^] I have done both Winforms and WPF and I have to say I like having a WPF codebase to maintain much more than a Winforms codebase to maintain. Databinding in WPF is a stellar experience. I've done one commercial product with it and it's a snap to maintain. WPF is very different though. If you haven't done a lot of winforms, you might be in better shape, not having your mind ruined by taking all the shortcuts winform so graciously allows.... I like this article by Lapthorn very much, because he's very deliberate about skipping the whiz-bang "unleashy" stuff and concentrating on what basics you need to know. Recommend you work through each example to see the evolution from wrong to right.... I did. Very informative hands on format. WPF is a paradigm shift from winforms for sure. The Hardest part for me was NOT looking for winforms equivilants in wpf. ("But it works like this in winforms waaah..." Just stop it already.) :-D