If you encounter the edit properties box on single document uploads and still want to run custom code in the ItemAdded event receiver, you will need to employ the method discussed in this article of converting asynchronous SharePoint event receivers to synchronous. The motivation behind this post was to avoid save conflict errors. But there are potentially other scenarios where it might be useful to make asynchronous SharePoint event receivers synchronous.
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.
My previous four-part series described how to set up a SharePoint development farm. Now, what if we want to take things a step further and configure our SharePoint farm to allow sending of outgoing emails? This article discusses everything you need to do to make this possible – from installing and configuring the SMTP service, to defining outgoing email settings in SharePoint Central Administration. I provide code examples as well.
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.
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.
I have often needed to manage web parts programmatically in SharePoint using the server object model. While the requirements have varied depending on the specific situation, common things I have needed to do include programmatically adding, deleting and/or moving either custom webparts or OOTB web parts. I have also had to programmatically modify some OOTB web parts using the SharePoint server object model. I have an example of how to do this for the content editor web part in the last section of this article. This article provides quick code samples to manage web parts programmatically. Copy and paste and enjoy!
Since PowerShell is now open source and cross-platform, we can now perform PowerShell magic right inside Linux boxes. If this isn’t exciting, what is?! Here’s an example of how to execute PowerShell scripts (or commands) from PHP code on a Linux VM.