I have done quite a bit of programmatic manipulation on the SharePoint quick launch bar in C# so I decided to write this article that logs some of the tips and tricks I have used. Here you will find how to add and delete items, update links and text in parent and children nodes, add headings (items without links), add links that open in new window, and handle audience targeting for specific quick launch links.
SharePoint developers and IT pros are familiar with the “sign in as different user” menu option in SharePoint 2010. However, in Microsoft SharePoint Server 2013, you will notice that this menu option is missing.
When we write code to handle the ItemUpdating or ItemUpdated list item events, we may sometimes need to take different actions based on whether the event was triggered by a regular item update or by a version restore operation.
Say you have a SharePoint workflow which runs whenever a list item changes (ItemUpdated). You also have some custom code to do some manipulation on the same list item at the end of which you need to perform an item update using one of the SPListItem update methods: Update(), Systemupdate() and UpdateOverwriteVersion(). You will quickly notice that this update will trigger another instance of the workflow for this item once the current workflow terminates. You have just hit an infinite loop.
When dealing with event receivers in SharePoint custom code, we use the BeforeProperties and AfterProperties to get a hash table of properties consisting of string/value pairs that correspond to fields in the SPItem object before and after the event occurred respectively.
Developers often need to set up sandbox development environments where they have full privileges to manipulate stuff. Here, I summarize the steps for setting up a SharePoint development virtual machine (VM). These steps apply to on-premise installations of both SharePoint 2010 and 2013.