Itemupdating folder fires twice
Therefore, any time you add a document to a document library, the : By design, Share Point Foundation raises events for all list items when the request is not bound to a content type.
This allows an event to be raised for all items when the event receiver is registered for all items in the list.
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.
We may never know about all of the dangers lurking out there, but today we’re going to cover at least one danger you may encounter while writing event receivers – an annoying issue with the Item Updating and Item Updated events firing twice.
I should also point out that I know the difference between a metaphor and simile in case that was bothering you from the opening sentence.
I am nothing if not a masterful linguist after a beer or two or more.
Programming events can cause exceptional behaviors, depending on the contexts in which you implement the event handlers.
The following describes event behaviors related to specific contexts that you might encounter when writing code.
If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site. Sometimes that is the most exciting way to learn, but for those less adventurous I will briefly cover the topic here.You can think of an item event receiver like a database trigger: it has different events that fire during the course of Share Point running an operation on a list item (or document item).Item Event Receivers derive from the SPItem Event Receiver class and have a number of methods that can be overridden to respond to various events: As you look through this list, you should notice that events have two types of endings: WARNING: One major gotcha you should know about the SPItem Event Receiver class is that while you can implement multiple list item event handlers in a single class, Share Point instantiates a new instance of that class for each individual event it needs to handle.
What this means is that you cannot store data in instance-level variables and share that data between event handlers.
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.