Sorry, but the simplicity of creating a simple GridView in WinForms can't be beat. Drop a grid on a form. Click on the grid to create a new data source and bind it. If you know how to do it in a simple easy way in WPF please tell me. I've been at it for 3 days to no avail. I got the WPF Toolkit and the WPF DataGrid. I must admit that it was very easy to do the data binding in C#. All it took was 1 line of code to set up the DataContext for the form. As far as the XAML goes it was not that easy. Yes, ItemsSource is in the intellisense list but that's about it. I had to do some googling and watch some videos in order to figure out the "{Binding Path={}}" part. Now I want to define some of the columns in my GridView. It would be nice to be able to bind during design time so that I can see what the layout would look like (same as I would do it using WinForms). I can't find any real help on that..... Another issue is related to the XAML intellisense. Where is the tooltip help that pops up with some guidance as to what each property, method and node does? We do have that in the code behind but not in XAML. In other words, we now have to learn a whole new language (XAML) in order to lay out our forms. We never had to do that with any visual designer up to this point. Don't get me wrong. I do like the whole concept of XAML. To be really usefull, I should be able to everything using the property pages without having to resort to XAML. The advantage is that grunt of the work will be done visually and you would go to XAML in order to tweak. This is the way that ASP.net development works right now. Lastly, since the layout is totally separate from the code (C# or VB), it would be nice to have the option to deploy the application with the XAML in a separate file. This way you could do some changes to the layout without having to recompile the whole app.

Oh my G-d..... And I thougth that I was alone in feeling the way I feel about WPF. I also have close to 30 years in the trenches. After reading all the marketing materials about WPF I decided that this would be the next "it". I started playing around with it and in concept it's not a bad idea at all. Or is it? Why push all the properties of a control to XAML when you can keep them in the properties window? Why am I being forced now to remember all the properties and settings for control when beforehand all I had to do was scroll up and down that properties window? At least give me some decent intellisense... I believe in simplicity. If I cannot bind data to a grid and lay it out the way I need it at design time, then I'm not interested. Maybe it's because the WPF controls are not mature yet. Besides, what is really the advantage of all XAML? I was reading an MS article thattells you what to do when your XAML gets so big that it chokes the visual designer. Their soulution? Easy. Hide the visual designer and work only in XAML? So what happened to the "visual" in Visual Studio?