This project is read-only.

SharePoint Solution Deployer 4.0

Rating:        Based on 2 ratings
Reviewed:  2 reviews
Downloads: 924
Released: Aug 8, 2012
Updated: Dec 20, 2012 by matein78
Dev status: Stable Help Icon


application, 31K, uploaded Dec 18, 2012 - 924 downloads

Release Notes

How to use SPSD SharePoint Solution Deployer

(v4.0.3.8989) Minor Update to fix AllowCASPolicy/AllowTrustBindeployment switch SP15
(v4.0.3.8623) Package has been updated to support SP2013 RTM

Attention: Make sure to "Unblock" the zip file before extracting. Otherwise you have to unblock each bat and ps1 file one by one to get the script running.

This is the first release of a complete rewrite of SPSD in PowerShell!

  • Deploys, retracts and updates one or multiple WSPs
  • Deploys Farm and Sandboxed solutions
  • Checks prerequisites before deployment (i.e SharePoint version/license, installed WSPs, Admin permissions, remote access to all servers in the farm, services running etc.)
  • Optionally runs your custom PowerShell scripts (.ps1) or commands
  • Available targets:
    • BeforeDeploy, AfterDeploy,
    • BeforeRetract, AfterRetract,
    • BeforeUpgrade, AfterUpgrade
  • Optionally performs actions on one or all servers (by using PSRemoting) in the farm, like
    • IISreset,
    • Recycle AppPools,
    • Restart services like SPTimerV4, SPAdminV4, SPUserCodeV4
    • Warmup server urls (avoids the load balancer to warmup on all machines in the farm)
  • Easy configurable for different environments (create custom environment configurations which are automatically used based on machine or user name)
  • Allows to split environment definition in multiple files to reuse parts for different target farms (DEV, INT, ACC, PROD)
  • Detailed deployment log file
  • Implemented entirely in PowerShell (2.0 or higher required)
  • Supports SharePoint 2010 and 2013 Preview

How to use it:
  1. Download SPSD and unzip it
  2. Drop your WSP files into the "Solutions" folder
  3. Copy everything on one server in your farm
  4. Run the Deploy.bat

For more detailed control over the deployment process you can
  1. Modify the 'default.xml' environment definition XML in the "Environments" folder
  2. Create your own environment file in the "Environments" folder. If you name the file after a machine '$env:COMPUTERNAME.xml' it will be used instead of the 'default.xml' on that machine, if you name it after a username '$env:USERNAME.xml', it will be used when the script is run by this user
  3. Extract any XML node of a configuration file to a separate file and specify the ID and FilePath tags. SPSD will automatically merge the files together. This allows you to reuse parts of the configuration for different deployment environments.
  4. Specify variables in the environment definition file, which will be replaced on runtime (you can also use system environment variables)
  5. Specify custom PowerShell commands (i.e activate features, run your own scripts etc) in the 'Scripts/CustomTargets.ps1' file in the corresponding target.

Reviews for this release

Hell Great :)
by faisalrafique on Nov 21, 2012 at 9:39 AM
A top of the line tool for a consistent deployment!
by dknyoli on Sep 5, 2012 at 3:29 PM