Itemupdating which wasn t handled
Damon gives just one example of a poisoned dagger in the game of Sharepoint Development: The Item Event Receiver.
I’m usually disappointed when writers employ oft-overused metaphors to describe a situation.
Simply put, the Item Updating and Item Updated fire twice when adding a document to a library that has the Require Check Out option enabled.
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.
If you find yourself in this situation, then you’ll have to solve the problem in code.
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.
With that in mind, Share Point 2010 is like a sea of icebergs – there is a lot going on under the surface that you may not notice until it’s too late.
Unfortunately, that makes your project like the Titanic.
Hopefully you know about item event receiver if you are having problems with them firing twice.
If not, kudos to you for tackling the object model with reckless abandon.
Search for itemupdating which wasn t handled:
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.