title: CellValueChanged vs CellValidating Events for DataGridView
body: <p>What's the best place to implement validation logic code and conditional formatting code for a DataGridView?</p>
  
  <p>In a lot of books and articles that I've read on this control, it seems to suggest that the appropriate event to handle for this is the CellValidating one.
  Well, the name more than implies this as well.</p>
  
  <p>However, this event triggers a bit too often for my tastes and I'm not sure it is required.
  For example, this event triggers everytimes the users switches to another row.</p>
  
  <p>On the other hand, the CellValueChanged event seems to trigger only when the value of the cell changes, which means the validation code runs only when the value changes and not everytime a user changes cells.</p>
  
  <p>Now, since so many books use the CellValidating event, I wonder if there is not any gotcha (in display for example) with using the CellValueChanged?</p>
  
  <p>I understand that the impact in performance should be irrelevant when using simple validation and conditional highlighting rules but I would as much prefer it not to run useless code everytime the user moves to another cell if it can be avoided.</p>
  
  <p>Thanks,</p>