The event receiver was nicely attached and got busy when I uploaded a document. I was trying to change permissions on an item and this was the part of my code that was creating the problems: Inside my SPRemote Event Type.Item Updated I did an Update and making it trigger itself. If you’re dealing with a event receiver with access to server side code, this is not a problem.By comparing the values in the before Properties with the after Properties I could see if they contained a difference.
I became curious, though, and wanted to see how it worked.
Time to use Share Point Dev Tool #1 (Reflector) on the SPEvent Receiver Base class…
Your add-in can handle the following list and document library events.
Events ending in "ing" are before (synchronous) events and those ending in "ed" are after (asynchronous) events.
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.Note The name "apps for Share Point" is changing to "Share Point Add-ins".During the transition, the documentation and the UI of some Share Point products and Visual Studio tools might still use the term "apps for Share Point".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.