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.
What this means is that you cannot store data in instance-level variables and share that data between event handlers.
For example, if you define an instance level variable in the class to store data in the Item Updating event, then try to access that data in the Item Updated event, you will find that the data is not there when you go to check it in the Item Updated event.
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.
And proud MEET member If you don’t find the answers to your questions on this blog, you can always post your questions to the Share Point 2010 forum or the Share Point 2013 forum.
Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.
Users can change data like the number of moons or the distance to the earth, but they are not able to change the name of the planet.
To prevent users from changing the name of the planet, you can develop a Item Updating event receiver.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.