title: NHibernate, WinForms, and DataBinding - do they play well together?
body: <p>I've been using WinForms databinding to display data from a database mapped with Fluent NHibernate, and that's been working great. </p>
  
  <p>For example, I can just set a DataGridView's DataSource property from an entity's IList property, and voila - there's all the data!</p>
  
  <p>But now I need to start adding and saving new data rows, and that's not going so well.  I thought I'd be able to just enable the grid's AllowUserToAddRows property, and new rows would get added to the underlying IList in the entity, but that didn't work.</p>
  
  <p>Then, after a little searching, I tried setting the DataSource property to a BindingList that was populated from the IList, but that's not being updated with new rows either.</p>
  
  <p>During the course of my searches, I also came upon a few people reporting difficulty with WinForms and DataBinding in general, which makes me wonder if I should pursue that approach any further.</p>
  
  <p>Is the DataBinding approach worth continuing?  If so, can anyone suggest where I'm going wrong?</p>
  
  <p>Or is it better to just handle all the DataGridView events associated with adding a new row, and writing my own code to add new objects to the IList property in my entity? </p>
  
  <p>Other suggestions? (though I don't think switching to WPF is going to be an option, no matter how much better the databinding may be)</p>