The first time the Item Updating and Item Updated events fire it is in response to the document properties changing.
The second time they fire it is in response to the document being checked in.
Unfortunately, that makes your project like the Titanic.
I don’t mean that it’s largest and most luxurious application every written, but rather that you may be cruising headlong into a nasty rendezvous with an iceberg that could deal a severe blow to your project.
If not, kudos to you for tackling the object model with reckless abandon.
I’m Karine Bosch and currently I’m working as Share Point Solution Architect for Recomatics, a company located in Destelbergen near Ghent.
To understand why this is happening, let’s first look at what happens when the user adds a document to the library when the Require Check Out option is disabled: So the net result of this is that the document is uploaded and the Item Adding and Item Added events have fired, which is pretty much what you would expect.
Next, let’s look at what happens when the user adds a document when the Require Check Out option is enabled.
Previously I worked as a Premier Field Engineer for Share Point @ Microsoft Belgium.
For 5 successive years I’ve been rewarded as Share Point Server MVP for my contribution to the Share Point community: I developed the U2U CAML Query Builder and its successor the CAML Designer, which I develop together with Andy Van Steenbergen.