Itemupdating not dating someone completely opposite
I’ve got an event handler on a Share Point list that’s fairly long running, and this then raised a question in the office – do these settings control event firing for the currently running event handler, or for the entire list? A quick check on twitter suggested the same – that it was the thread (thanks @Chris O_Brien). The setting (Disable Event Firing in 2007 and Event Firing Enabled in 2010) must be for the current event handler; if it was the entire list there’d be all sorts of timing issues and weirdness, and a thousand developers would already have screamed in agony.When you are working in Visual Studio, and you add a RER to a Share Point Add-in project, the Office Developer Tools for Visual Studio do the following: When a registered event occurs, Share Point calls the appropriate method in your service and passes an object that provides some context information for your code.For example, the event type (from one of the two tables earlier in the article) is identified, so that your code can branch to the logic that is appropriate for the event.
(I’ve not tried this.) Finally, if you wanted to turn off or on event firing from your own code, without an event handler – like if you were creating a number of items from a console application, etc.Note Website events and site collection events are not supported in Share Point Add-ins.There are two kinds of events: To handle list and list item events, you create remote event receivers (RERs), which are web services that run externally to the Share Point farm or Share Point Online.This was my scenario: I had created a remote event receiver that was attached to a document library and was supposed to act whenever an item in the list was updated.
The initialization of the event receiver looks like this: And all was fine in the world.
The URL of the RER service is registered for the events it handles.