PowerShell desired state configuration scripts often request user credentials which then need to be stored in some form in the output MOF files. Since you never want to save passwords as clear text, this article explains how you can keep passwords secure and encrypted inside your MOF files.
Access requests can be configured per site in SharePoint site settings. And there are quite a few PowerShell scripts out there to set the value of the email address that receives the notifications. However, what if you prefer to completely turn off the site access requests feature for all your websites in one shot, and then just display an access denied message when necessary? This article provides a PowerShell script for that purpose.
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.
I have been playing a lot with PowerShell desired state configuration (DSC) recently and so, I decided to write an introductory post on it. In this article, I explain at a high level what PowerShell DSC is all about. And then, I provide a simple example that demonstrates at a basic level how PowerShell desired state configuration works.
If you work with content migration in SharePoint sites, you may often need to save lists and libraries as templates so that you can re-use them in other sites. This article shows how to fix the error that occurs when the list template maximum size is greater that 50 MB (or 52428800 bytes).
Generally, when writing code to communicate with web services in C#, the usual process is to add a service reference. Visual Studio then automatically creates all the wrapper classes/objects for you that you need in order to talk with the service. However, sometimes, you want greater control. This article explains and gives you the code needed to work with a regular SOAP based web service without adding a reference.