SharePoint: Deploying WebPart/Feature as SharePoint Solution Package (.wsp file) - Part 4

Link to Part 1 : Creating Skeleton.

Link to Part 2 : Creating Features/Webparts

Link to Part 3 : Creating .ddf and Manifest.xml

Link to Part 4 : Using STSADM and Centeral Admin to add and deploy solution (current post)

Upon successfull completion of build, you will se two additional folder, in bin\debug directory. Namely:

• cab: contains cab file
• wsp: contains wsp file

reason for creating cab file is:

• to verify is all referenced file are included in the solution
  
• to verify file heirarchy

Upon successful verification of solution, we move forward on how to deploy solution in SharePoint 2007.

Deploying the solution file to SharePoint is a two-step process: First, register the solution in the database. Registration is accomplished from the STSADM command-line utility. To add the test.wsp file, run the utility like this:

STSADM –o addsolution –filename test.wsp 

Second, once the solution has been added to the solution store you can deploy it from the command line, or you can deploy it using the Central Administration user interface. Find the Solutions Management page by going to Start-->Administrative Tools-->SharePoint 3.0 Central Administration-->Operations, and in the Global Configuration section clicking Solution management. From there, click one of the listed solutions to see its status and to take action on it—like deploying it.

Alternatively, you can deploy the solution from the command line with the STSADM command deploysolution. If you want to deploy the test.wsp solution to the local system, issue this command:

STSADM –o deploysolution –name test.wsp –allcontenturls –local –allowgacdeployment –allowcaspolicies 

The –allowgacdeployment and –allocaspolicies options are necessary only if you have indicated deploying an assembly to the GAC, or you have provided a CAS policy as a part of the solution file, respectively.

Hope this helps !!! 

Cheers