English SharePoint Solution Deployer, by Matthias Einig has been around from 2012. You can find it in Codeplex - SPSD SharePoint Solution Deployer here. Initially it was targeted for SharePoint 2007 deployment but has been evolved many times and now it support SharePoint 2010 and SharePoint 2013. There is big change from SPSD SharePoint 2007 and SPSD SharePoint 2010⁄2013 version. The former is using MSBuild task to perform the delivery, while the later is using PowerShell to do the delivery.
English After the 3 series of Progressive Solution Installation Package using Nuget, many are asking whether we can streamline the process to create the installation package. My answer is YES. Today I want to introduce Installation Package MsBuild which has been published through Nuget. To start using this tools, type in your Visual Studio package manager. So, what will it does? The InstallationPkgBuild will convert any .NET project (library, console, SharePoint etc.
Many of our folks in the field rely on SharePoint Farm Version number information in Central Administration to compare the patch level between servers. While this number is showing the latest SharePoint Foundation, it doesn’t always mean that you have a completely patched SharePoint farm. The reason, because Microsoft releases many different type of patches:
Cummulative updates (CU) Server packages (Uber packages) Public updates (PU) Stefan Gossner wrote an excellent blog about SharePoint patch terminology and the impact your farm patch level in “SharePoint Patching Demystified” .
English Previously in the part-1 and part-2, we discuss the problem to create installation package in a complex project. We choose to use Nuget package instead of creating MSI, as Nuget implements OPC and very close to developer activities. Moreover it still serve our purpose to create versioned package, where version number of the installation package is embedded in the package itself. In this part, I continue to provide an example to package SharePoint Solution (WSP) into an installation package.
Yes, starting from this month bi-monthly SharePoint CU will become a history. From July 2014 Microsoft will release CU every month - yes EVERY MONTH!. So forget about bi-monthly. With this change policy, we expect that Microsoft will be able to address problem more quickly. The drawback, we know there were incidents in the past that some patches / CU were not going well. Microsoft subsequently released updated patch after releasing the patch / CU.