The handler simply creates a task in the Tasks list corresponding to the new item added to the custom list.
I am able to fire an Event using an Event receiver which I created using Visual Studio 2010 on a custom list.
After creating the simple project, the problem was still there.
The event wasn’t firing twice for the same list, it was firing for ALL Lists.
When I added it to the list instance, it just caused the event to fire twice on THAT list.
If yes, then deactivate the feature and delete the duplicate receiver.
I have checked the SP Manager 2010 and it says its registered twice.
Then, created a new feature and event receiver from scratch and deployed it.
As with any problem, I always try to resolve it through the process of elimination by first isolating the core issue into a test project and therefore out of the primary project I’m experiencing it in because sometimes you can’t see the forest because of the trees.
Still, it was getting registered twice instead of once.vti_sourcecontrolcheckedoutby in the before and after properties is always null during my actual updates so I can just check that.
When Item Updating is called after Item Added both are populated with my username I have same problem as yours, can you please tell me what is the statement you are using.
Apart from voyeurs, others who were disappointed with ban on You Tube were spammers and squatters who would have uploaded a random slideshow of old photographs of Hina and Bilawal, with their website’s URL on every slide, and putting the title of the clip as EXPOSED: HINA & BILAWAL CAUGHT HAVING SEX.
Most hilariously, when a police witness mounted Ahuja’s skullcap (a piece of evidence) onto a dummy skull, also used the oldest tricks in the book — headlines and visuals — to captivate and sway readers.