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.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.

sharepoint event receiver itemupdating beforeproperties-4sharepoint event receiver itemupdating beforeproperties-47sharepoint event receiver itemupdating beforeproperties-40

Event recievers are common in Sharepoint development so its better to understand the data available in each events.

Sometimes as a developer we jump into coding before thinking about contextual data availability.

Does someone have any tips of other ways to Compare the values?

Get Item By Id(list Item ID); var moderation Status = item["_Moderation Status"] as string; if(moderation Status == SPModeration Status Type. To String()) //Do stuff But before Status and after Status is null.

I don’t mean that it’s largest and most luxurious application every written, but rather that you may be cruising headlong into a nasty rendezvous with an iceberg that could deal a severe blow to your project.

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.You know the After Properties subscript operator returns an object right? Shouldn't you be casting to a string or calling To String()? I should also point out that I know the difference between a metaphor and simile in case that was bothering you from the opening sentence.I am nothing if not a masterful linguist after a beer or two or more.This is true for Share Point 2010 and Share Point 2013 and its present only for custom lists but not for document libraries.