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.
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.
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.
English It is rare that in real-life project that we only deliver 1 SharePoint Solution using WSP in the installation package of our solution. Even in very simple case, the installation package must contain at least Release Notes, Installation Guide which is not part of WSP. In more complex case, the installation package must also contains scripts, batch file, reporting services files, windows service installation and many more. Yes, we can create custom MSI and put all of those items together in the installation package as our ancient did.
Few month ago I have introduced RemoteStsAdm, a PowerShell module that enable you to execute StsAdm.exe remotely. StsAdm.exe is a command line administration tools for SharePoint. Unfortunately to run StsAdm, one must log-in to SharePoint server member – since the tool can not be executed remotely. RemoteStsAdm is to answer this problem, allowing admin to execute StsAdm remotely. You can download the source code from MSDN Galery here or read the original article in previous post here.
SharePoint 2010: RemoteStsAdm PowerShell Module is available via NuGet | Ideas For Free - Dec 0, 2011[…] PowerShell: Introducing Import-PSModule […]
Very promising. I'm wondering if the nuget repository could be a file share, like it should be possible within VS… thx for your great job
Yes, it is possible to use file share for nuget repository. However, there is a drawback since you can't query latest package. Nuget will return all packages, which mean additional task for client to filter it.