>Hmmm... Unless you added them since the weekend. It looks like I went brain dead and missed them. Getting so frustrated trying to solve the binding of an xceed datagrid to a Ling to SQL query I can barely see straight. arg

>No WPF and XAML are somewhat synonymous in my mind. I don't think we need separate categories unless you start getting a ton of posts in WPF.
>
>>Hi,
>>
>>WPF and WCF categories were added recently. Since XAML is so intrinsic to WPF do you think it should have a seperate category?
>>
>>Regards,
>>Viv
>>
>>>I notice there is no Category for either XAML, or WPF. Is anybody here doing much with these?
>>>
>>>Part of the reason I ask is I Posted a question MESSAGE#1295934 over the weekend, and got no reply. No biggie, but I was also curious to find out if people are seriously considering switching over to it, or if it's still not quite up to par.

Guess I missed that post. Was it about the Xceed grid mentioned above? Not familiar with the grid but are you trying to bind to a 'Table' object (i.e. one created by VS in a dbml file)?

As far as switching goes: we are seriously considering dumping two or three months worth of Winforms development in favour of WPF - but mainly because the app is question is strongly grahics orientated and the WPF retained graphics architecture makes a *lot* of things much simpler.
Also WPF provides the opportunity to farm out some of the UI look and feel to design oriented people (ala web design). They're playing with Expression Blend but it's probably a version or so away from being really usable - one current annoyance is its inability to integrate into source control.

The WPF downside, from a graphics POV, seems to be that when you need to do something that *isn't* built-in it's actually *more* difficult than using the winforms stuff that was more closely tied to GDI+. So our jury is still out on this. We probably need to investigate the viability of combining WPF and WinForms components.

Just my 2cents....