In the many years I worked for U2U, I worked as technical assistant for Patrick Tisseghem who unfortunately died on 3th September 2008.
Together with Patrick we developed the alfa and beta versions of the Silverlight Blue Print for Share Point which contains several samples on how to integrate Silverlight with Share Point. I’m also board member of the belgian user group BIWUG.
Step 1 is to check the type of Event that triggers this Event Receiver by making use of “SPRemote Event Type” Enum and “Event Type” Property of the “SPRemote Event Properties” object Step 2 is to check the List Title by making use of “Item Event Properties” collection of “SPRemote Event Properties” object and ensure that we are handling Delete Events received only from a specific which in our case is “Products” Step 3 is to check for the desired condition and if satisfied then set “Error Message” and “Status” properties exposed by “SPRemote Event Result” object.
In this case we have set a user friendly message and set status to “Cancel With Error”.
These properties let Share Point to terminate the Event generated and no updates to the Item will get persisted.
Finally Step 7 is to capture information about the Item and Event and write it back to Windows Event Log.
This feature already exists for a long time in Share Point, but as this question comes up regularly, I decided to write a post about it. If you now go to a document in a document library, and you click the Copy link button, you get a URL similar to this: If you rename a document, or move it, this URL still works.
Also URLs as follows will work, as long as the URL is a valid URL to an existing Share Point site, and as long as this Share Point site has the Document ID service feature activated: If you delete the site or the site collection afterwards, the URL will not work anymore, even if you moved the document to another location.
How workflow tasks are locked The first thing to realize is that when Share Point workflows alter tasks there needs to be some sort of locking behaviour on tasks so that you will not accidentally create race conditions and update a task simultaneously, the one update overwriting the other.
And proud MEET member If you don’t find the answers to your questions on this blog, you can always post your questions to the Share Point 2010 forum or the Share Point 2013 forum.