>>>>I will follow the links and read them. But are you saying that you write your business code in XAML too? No place for C#? And what about ADO.NET? Do you use XAML to manipulate ADO.NET objects?
>>>
>>>The business logic always goes in the code-behind (in C# for you) and the design stuff in the xaml. This article does the best job of explaining the separation and presenting different possibilities for good teamwork I've read (seriously):
>>>
>>>http://windowsclient.net/wpf/white-papers/thenewiteration.aspx
>>>
>>>note this statement in the article:
>>>
>>>Choose Code-behind
>>>Though WPF allows you to insert code inline with the XAML, this is not a recommended practice. Avoid it at all costs; placing code inside a XAML file breaks the separation between code and XAML, leading to a maintenance nightmare.
>>
>>Thank you. You make a good point that I was trying to say to Mike. He was trying to convince me that using WinForms is a waste of time. I disagreed saying that if/when I go with WPF I will still need to write BIZ classes, DAL classes, manipulate ADO.NET and C# and ADO.NET knowledge will be helpful.
>
>I agree, but none of that is winforms, but rather the language tool you choose to use for those layers. Winforms is only the method used to display the data to the user. It is only one of the layers.

I agree. Hopefully all the BIZ and DAL that I have I will be able to use in WPF too. As long as I can bind controls created in WPF to typed datasets.