Itemupdating which wasn t handled

The second time they fire it is in response to the document being checked in.It appears as though they are firing twice in this situation because Share Point is updating the properties on the document and then checking it in on the same request.Turning off the Require Check Out option is a great quick fix if you don’t require the item to be checked out in order for it to be edited.But that option exists to be used, and some people really do need it.Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.Dangers lurk hidden out there which, if you run into them, can be a blow to your project and waste a great deal of time.

These methods are just like the Item Updating and Item Updated methods in the SPItem Event Receiver class, but they have an additional Boolean parameter named is Check In that indicates whether or not the event is being raised as result of a check-in operation.If you were to check the document out and edit the properties on the document, you would see the Item Updating and Item Updated events fire once.Later on, when you checked the document in, you would see those events fire again.If the user opts to cancel, then only the Item Adding and Item Added events will have fired and the document will be left in a checked out state.Also note: the Item Updating and Item Updated events that fire in response to the properties being edited from the dialog will always occur, even if the user is not entering or changing any of the values.