I’m usually disappointed when writers employ oft-overused metaphors to describe a situation.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.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 board member of the belgian user group BIWUG.Remember that if you want to develop event receivers for specific lists, you will have to work with content types.I’m Karine Bosch and currently I’m working as Share Point Solution Architect for Recomatics, a company located in Destelbergen near Ghent.If the name isn’t changed, the changes are saved to the Share Point list.Before you can deploy the event receiver you have to change the file to bind the Update Adding event receiver to all custom lists.
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.
I am nothing if not a masterful linguist after a beer or two or more.
Hopefully you know about item event receiver if you are having problems with them firing twice.
You can also use event receivers to validate the data that the user wants to change.
This walkthrough is based on the first one where I have a custom list with planets of our solar system.
If not, kudos to you for tackling the object model with reckless abandon.