title: Why Use IEditableCollectionView?
body: <p>I've got a project I've got to crank out (thanks to an employee quitting on the job before the deadline).</p>
  
  <p>He'd been working in WPF. The interface looked cool, but it never was able to collect data from the company's old data access DLLs. (Rewriting the DLLs is a great idea, but not feasible in the short time left by the deadline) <strong>Collecting data was the whole point!</strong></p>
  
  <p>The project was thrown at me, but I'm no WPF developer. I've been told to make it work with WinForms, which is what I know. I had a WinForm interface cranked out in a few hours, and it looks every bit as good as the WPF version ...and I know what it is doing. WPF involves voo-doo I haven't learned yet.</p>
  
  <p>There are things used in the WPF project that I need to get a grasp of what they do, and I do not have time to completely redesign it all.</p>
  
  <p>The Business Logic Layer returns an <code>ObservableCollection</code> to the WPF interface.</p>
  
  <p>The WPF interface takes the <code>ObservableCollection</code> and stores it in a <code>CollectionViewSource</code> using its <code>Source</code> parameter.</p>
  
  <p>OK, I'm immediately thinking <code>DataGridView</code> control and using the <code>DataSource</code> parameter from it.</p>
  
  <p>Am I on track?</p>
  
  <p>What was the point of the <code>IEditableCollectionView</code>? Is it necessary? And if not, should I just remove all references to it?</p>