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.
I code in several different programming languages and I post content relevant to the different languages on this website. Software development tools and languages evolve very dynamically. What's hot today may be forgotten tomorrow. So, categorizing my content based on language is not very practical. Instead, I use client-server labeling to categorize my work with various programming languages. This section holds content that I consider to be back-end (or server-side) programming.
A very common requirement for SharePoint developers is to assign out of the box and/or custom SharePoint permission levels to sites (SPWeb objects) or lists and document libraries (SPList objects) or even list items (SPListItem objects).
Developers often need to parse an XML document in order to get XML document nodes, child nodes and so on. But usually we have no idea how far the depth/nesting of child nodes can go. So we need some form of recursive technique to loop the nested nodes and help us grab the values we want.
The idea here might look really crazy. But on a few occasions, I’ve had to loop through an entire SharePoint Farm in search of a list with a unique title (and then create the corresponding SPList object). One time I’ve had to do this was when passing control to an aspx page in the layouts folder from a modal dialog that was just closed.
I wrote this post as a follow up to my last post: Add Custom Action To SharePoint Edit Control Block. Just like with the edit control block, SharePoint Developers often need to add a custom action to the SharePoint Ribbon.