Jeremy D. Miller -- The Shade Tree Developer

Pingback from  actionsx » How you're writing WinForms apps - The results

Pingback from  Todrom.Com » How you're writing WinForms apps - The results

I don't understand the issues with Databinding being so troublesome... can you elaborate on the issues?

My typical use of databinding is that I have IList<t> collections and I assign them as the datasource in my view. i can still unit test against the presenters that load up the IList<t>... for complex databinding scenarios (where I need to actually update the list and have it reflected in a grid, etc), I wrap my IList<t> inside of an IBindingList<t> when i send the list to the view:

public IMyView.MyMethod(IList<whatever> whateverCollection)

{

 BindingList<whatever> bindingList = new BindingList<whatever>(whateverCollection);

 myGrid.DataSource = bindinglist;

}

from there, i can update the original IList collection from within my presenter and it shows up in the view automatically.

It would be interesting to hear what people answer if you were asking for WPF.

WPF is a giant hunk of crap, at the moment. (my personal opinion) and is not ready for prime-time use, by any means.

I tried implementing it for one of the most simple scenarios I could think of, in a recent project. it tooks two weeks to get a panel bar created and working (there are no good control suites for WPF, that i know of, yet) and the end result took 15 to 20 seconds to load the form, every time. I switched it out for a Telerik based standard winform in 2 hours and the form takes about 2 seconds to load.

@Derick. I don't think any WPF dev would deny that there's a significant learning curve to it. However, I can promise you - my personal opinion - that WPF brings many benefits to application developers once you grok it.

Did you try running existing WPF samples on your machine to check whether they had performance issues? To me, 15-20 seconds sounds like something may be wrong with your installation / hardware / code. Trying an existing sample would at least rule out your code.

@Derick

I have to disagree as well based on my experiences.

I've been prototyping a large data visualization project in WPF and the performance has been incredible!  I'm accomplishing things with WPF that would NOT BE POSSIBLE by my talent in GDI or using Direct X.

I've been using Infragistrics controls for WPF.

I must admit, I don't use the beta designers VS2005 or beta 2008.  I hand code the XAML to assist in groking WPF.