Fired event itemupdating which
This is because in Dispose method of Event Receiver Manager I’ve enabled the event firing. If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.This event is fired every time you make a change and save your list item.If you have a hook in place you can view the entire content and its current values in Event Receiver.Share Point as most us know, has built in workflow capabilities.In SP 2010, workflows have been made pretty obvious.
For disabling event receiver to get fired again we can use the property ‘’ as shown below: However, if you are in a webpart and want to modify an item but don’t want to fire event receiver, then? So if you can set your current’s thread’s data to the required value before/after updating item, you can control the event receiver.So, enough of theory, let’s get hands on and build our own Event Receiver feature for Share Point 2010.Step 2 The Share Point Customization Wizard will come up as shown below.You will notice as a part of the Event Receiver you’ve a cs file and an xml file called The Elements file is a kind of glue that binds your code to SP Event framework. element is a placeholder for the full assembly name.
The following code snippet shows my custom Event Receiver Manager: The code snippet above is derived from Share Point’s SPEvent Receiver Base to use the ‘Event Fireing Enabled’ property.