Itemupdating which wasn

I had already covered all the basic things such as: I even went as far as completely emptying the body of the handler to see that in fact the event was firing twice.

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. 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. I took another look at my event receiver I had added via Visual Studio to the project. Yes, I had left the file for the Event Receiver there, and therefore when the feature was activated for the project, the receiver got associated to ALL lists on the site.

I guess one of the reasons why is that I think its good practice and hasn't caused me any problems.

So the question is: What is a good technique that can be implemented such that I can check whether a specific column in a list changed in the The blog post James's colleague wrote is wrong.

It also lets you indicate that the delete operation should be canceled.

object will be used for both the updating and updated events, and that instance won't be reused in the context of a separate update. To String() since it converts nulls to empty strings. At that point you will not have Before Properties to compare to.

Every time an item was added to the custom list, the event was firing twice.

I was associating the event receiver to the custom list through Feature Activated on a feature receiver for my Event Receivers project.

Leave a Reply