I've bound and Item Updating event to a document library of a MOSS publishing site, I’m then trying to compare the Before and After properties. I'm sure this is probably a subset so make sure you test.
If via Share Point default edit form all columns are present in afterproperties collection, but if you edit an item from custom code (e.g.
webpart, event receive) only updated columns are present in that collection.
When accessing a user field in event receivers there are few differences in the returned values when Classic mode authentication is used from the value when Claims based authentication is used.
The difference is present in After Properties of Item Adding and Item Updating event.
Developing a Sharepoint application would have all the fun of a video game, if only you had infinite lives.
Dangers lurk hidden out there which, if you run into them, can be a blow to your project and waste a great deal of time. Content Types[content Type Name]; SPField Collection fields = content Type.Event recievers are common in Sharepoint development so its better to understand the data available in each events.Below are shown the results only for the events that have this problem.At the end of this post you can find the complete test results for Share Point 2013.Damon gives just one example of a poisoned dagger in the game of Sharepoint Development: The Item Event Receiver.