Sharepoint spitemeventreceiver itemupdating

The migration would have been faster if after adding each file the migration tool was waiting for the event receivers to complete because after adding all the files at once 90 % of the time the process was spending in switching between the few hundred threads and only up to 10% were the actual threads running the event receivers.The next interesting question is what is the lifespan for the SPItem Event Properties that are passed to all item event receivers (synchronous and asynchronous).The problem will be encountered if you have an Item Added event receiver attached to the document library that updates fields of the list item/document after it has been created.

So this means that all synchronous event receivers will share the same properties and all asynchronous event receivers will share different instance of the properties.However the unmanaged SPRequest class will keep the changes to the properties done by the synchronous event receivers and will pass them to the asynchronous event receivers.This means that it is generally possible to store information in the SPEvent Properties from some event receivers that could be passed to other event receivers executed later on.This would result either in the Edit form to not show the updated fields or in an exception to be generated when you click OK.In order to solve the problem we need some code to wait for the event receiver to complete before loading the Edit page.

Leave a Reply

  1. gay dating tennessee 08-Feb-2017 05:14

    Instantly stream, or download among any of our 114,000 porn videos! We offer tens of thousands of high-res pictures, full-length HD porn movies, our own comprehensive sexipedia of downloadable DVDs, popular featured pornstars, steamy XXX live cams and even a sex dating network!

  2. Afrika xxxsex com 10-Dec-2016 20:51

    Ackles: You'll have to wait and see, but pretty much.