Using Cmdlet with Powershell 2010
Tuesday, April 19, 2011 | Author: vrey
get-spserviceinstance | where-object { $_.typename -match "user*" }
get-spserviceinstance | select-object typename, status
get-spfeature | where-object { $_.displayname -match "custom*" }

add-spsolution -literalpath C:\customfeature.wsp
stsadm -o deploysolution -name customfeature.wsp -immediate -allowgacdeployment -url http://sharepoint:123

stsadm -o enumsolutions
stsadm -o retractsolution -name customfeature.wsp -url http://sharepoint:123 -immediate
stsadm -o execadmsvcjobs
stsadm -o deletesolution -name customfeature.wsp -override
stsadm -o canceldeployment -id 41db30bc-e54a-4791-91b5-df20d64f701f
stsadm -o deactivatefeature -name monthlyblogpost -url http://sharepoint:123
Failed to find the XML file at location '14\Template\Features\customfeature\feature.xml' -> here is the location where the feature is installed
uninstall-spfeature -id 4a33037a-23bb-42c5-b494-ee54eaadb212

Built Result:
Active Deployment Configuration: Default
Run Pre-Deployment Command:
Skipping deployment step because a pre-deployment command is not specified.
Recycle IIS Application Pool:
Recycling IIS application pool 'SharePoint - 123'...
Retract Solution:
Deactivating feature 'CustomFeature_Feature1' ...
Retracting solution 'CustomFeature.wsp'...
Deleting solution 'CustomFeature.wsp'...
Add Solution:
Found 1 deployment conflict(s). Resolving conflicts ...
Deleted file 'http://sharepoint:123/_catalogs/wp/CustomFeature_VisualWebPart1.webpart' from server.
Adding solution 'CustomFeature.wsp'...
Deploying solution 'CustomFeature.wsp'...
Activate Features:
Activating feature 'CustomFeature' ...
Run Post-Deployment Command:
Skipping deployment step because a post-deployment command is not specified.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Source: Steps To Install WSP file in STSADM
|
This entry was posted on Tuesday, April 19, 2011 and is filed under . You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

0 comments: