>>>I can't remember the books which others here have referenced to learn WPF, but I'd appreciate it if that person or persons here on UT could list those books again. I am due for a trip to BORDER BOOKS real soon and want to get at least one WPF book. I was up at 3:30 AM reading C#, watchign C# videos, and just plain excited about all the cool stuff. I let C# go for a few years and came back and voila!, it's all new again.
>>
>>I don't recall what was on the book list that was posted but, FWIW, my favourite is "Pro WPF in C#2208" from Apress.
>>Important point: read the introductory sections *slowly* and *carefully*. I intiially made my usual mistake of skimming this in order to get to the nitty-gritty........
>
>That's the one I started to go through.
>
>It made it very clear that WPF wasn't what I wanted to do (at least with the complete lack of worthwhile tools now).
>
>At some point Microsoft will force Windows developers to use it or die (just like they did for so many of their other wonder technologies that were the next great thing). They'll already have the technology that will kill WPF in beta at that time.
>
>That doesn't mean I'd be doing my customers a favor by writing more complicated and costly apps because Microsoft wants me to. I'll wait until I find no viable alternative or the technology actually becomes worthwhile for the customer - not Microsoft.

What is your defintion of 'more complicated'
Do you mean WPF apps are more complicated to write or more complicated to use.
If the former then I'd disagree - there is no reason to believe that developing a WPF app is more complicated than developing a WinForms one.
If the latter (i.e. more complicated for the end user) then it's probably irrelevant - you can write user-friendly or user-unfriendly apps on any platform. I find it easier to write user-friendly stuff using WPF.

And what leads you to believe that developing a WPF app would cost more than a WinForms app - are you factoring in the cost of your learning the platform ? If that's the case then all they need do is to use someone who already knows it (g,d&r)

>
>>>
>>>Cecil
>>>
>>>>Others have pointed out that the main thing is the move away from GDIplus and User32 to DirectX and a new User Interface layout system. But there are other useful features in WPF - for example routed events (and the Commanding system), better databinding possibilities and a new printing sub-system.
>>>
>>>>Warning: if you dive in to WPF you will initially find it *very* frustrating.
>>>>Advice: Dive in :-}