>Never learn to snow plow ! <bg>

LOL!! That's hilarious!

~~Bonnie




>
>>Just because WPF happily generates a "starter" WPF Window for you doesn't mean it's the best way to start.
>>
>>Think about it this way ... when you add a new project to a solution, what's the first thing that VS automatically does, besides adding the new project? It adds an empty Class1 for you. Gee, thanks, VS ... that's just what I wanted in my new project. First thing I always do is delete it. This could be either WPF or WinForms, doesn't matter.
>>
>>And don't get me started on dragging and dropping stuff from the server explorer directly onto a WinForm so that all the DataAccess is directly tied into your Form. Sure, it makes it easy to dummy something up real quick, but is it a best practice? Hell no!
>>
>>Do you see my point?
>>
>>~~Bonnie
>>