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” .
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.
English We continue our discussion to create installation package for our complex project. To remind you, a complex project is a software development project that delivers many component in the BOM (SharePoint WSP, scripts, batch files, etc.) See part-1 here. Defining Package Format As the title suggest, our package format is Nuget. Nuget is the package manager for the Microsoft development platform - so we expect that every developer is familiar with the tool.
This morning one of our fellow team reported that some of our applications stopped working. He thought that his recent modification caused the issue. He made initial findings and troubleshooting with no success - and finally he shared some debugging messages -
System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr) +41 System.Security.Cryptography.Utils._GenerateKey(SafeProvHandle hProv, Int32 algid, CspProviderFlags flags, Int32 keySize, SafeKeyHandle& hKey) +0 System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle) +699 System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair() +85 System.