Deploying SharePoint Solution Packages

After you develop SharePoint solutions in Visual Studio 2010, you can customize how the package files (.wsp) are deployed to the local SharePoint server.

Deploying Packages

You can deploy your package files to the SharePoint server on your development computer for testing and debugging. You can also create a package file that you can install on another computer. For more information, see How to: Deploy a SharePoint Solution.

To learn how to deploy a list definition, add an event receiver, and use the Feature Designer and Package Designer, see Walkthrough: Deploying a Project Task List Definition.

Customizing the Deployment Process

The following table shows the two deployment configurations that you can use when you debug and deploy a SharePoint solution.

Deployment Configuration



The default deployment configuration. The following deployment steps are performed.

  1. Run Pre-Deployment Command.

  2. Recycle IIS Application Pool.

  3. Retract Solution.

  4. Add Solution.

  5. Activate Features.

  6. Run Post-Deployment Command.

When a package is uninstalled, the following retraction steps are performed.

  1. Recycle IIS Application Pool.

  2. Retract Solution.

No Activation

This deployment configuration runs the same steps as the Default configuration, but skips the activation step.

You can create your own deployment configurations to complete a single step or change the order of the steps in the deployment process. For more information, see How to: Edit a SharePoint Deployment Configuration.

You can also add commands to run before and after deployment. For more information, see How to: Set SharePoint Deployment Commands.

See Also

Other Resources

Packaging and Deploying SharePoint Solutions