There are different base classes from which you can inherit when developing event handlers.
In the many years I worked for U2U, I worked as technical assistant for Patrick Tisseghem who unfortunately died on 3th September 2008.
Together with Patrick we developed the alfa and beta versions of the Silverlight Blue Print for Share Point which contains several samples on how to integrate Silverlight with Share Point. I’m also proud board member of the belgian user group BIWUG.
In that case you can wrap your update code in the following construct: I’m Karine Bosch and currently I’m working as a freelance O365 and Share Point Solution Architect .
I still do a lot of work for my previous employer Recomatics, a company located in Destelbergen near Ghent.
An event receiver is a piece of managed code that responds to Share Point events when specific triggering actions occur on a Share Point object.
Triggering actions include activities such as adding, updating, deleting, moving, checking in, and checking out.
Event hosts are common Share Point objects that expect to receive events—in other words, objects whose event receivers "listen" for Share Point events.
These Share Point event host object types include instances of common objects such as Share Point site collections, sites, and lists.
Although this script absolutely fails when testing in Test mode or an actual server instance, when I press the play button, everything works 100% fine. Is this an actual bug or is it a fault in my coding?