>>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)?
>
>The weekend post was this one MESSAGE#1295934. I haven't solved it yet, but was looking at trying to play with visualparent to see if I could get what I needed.
>
>What I've been stuck on is MESSAGE#1296509 I can get the grid to show up by binding to it from the code behind. But I can't bind to it from the XAML and that seems to leave the columns unsortable.
>
>The table is an IEnumerable object created using a Linq query. I used a technique of Rick Strahl's to make it passable. It's not the dbml table because I needed to do a join to get the data.
>
>>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....
>
>Good data, My understanding is that MS is not doing further development on winforms and is switching to WPF. I'm just getting going on most of this and don't have a hefty investment in winforms, so I figured I should check this out.
>
>curious... have you tested it on any older boxes to see how it performs. I'm going to need to test that soon as I have a wide range of machines in my environment.

Hi,
We haven't tested on any low end machines - but, from a graphics POV, the related WPF classes seem not only, as mentioned, simpler to use but also are noticeably smoother and faster then the older System.Drawing namespaces. That said I suppose we could have optimized the Winforms version by doing more buffering etc but WPF takes care of that right out of the box.
Best,
Viv