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.
This article discusses how to create a timer job for deleting orphaned users (SharePoint users that are deleted or disabled in AD) using Visual Studio. I have tested this solution on both SharePoint 2016 and SharePoint 2010. So, it would of course also work for SharePoint 2013.
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.
If you perform any automated website or list/library creation in SharePoint, you would at one point or another need to define and add fields (SPField) via code using the AddFieldAsXml method of the SPFieldCollection class. This article focuses on a few “gotchas” you may encounter while working with this method.
Depending on the folders into which items are uploaded in SharePoint, you may want to set default column values so that instead of a global column default value, your default values become folder-specific. This article demonstrates how to do this using C# code on a SharePoint 2016 server. The code can be added to event receivers to keep child items updated when something changes somewhere.
This article addresses an error associated with “ChannelOperationTimeout” when using Visual Studio to deploy SharePoint WSPs. The issue is generally associated with either very slow virtual machines, or very large SharePoint WSP package deployments.