5. Solution Package
• What is a solution package?
– A solution package is a distribution package that
delivers your custom SharePoint Server 2010
development work to the Web servers or the
application servers in your server farm.
– Use solutions to package and deploy custom Features,
site definitions, templates, layout pages, Web Parts,
cascading style sheets, and assemblies.
7. Sandboxed Solutions
• Allowing site collection administrators to deploy solutions that are safe to run.
• Deploying Solutions at Site Collection Level.
• Some of the Limitations are
– Can’t support visual web parts, because it contains a .ascx control that must be deployed to
the “_layouts” directory and deploying controls isn't allowed in any directory in sandboxed
solutions.
– Upload the solution package to the Solution Gallery and activate it.
– For Debugging sandbox solutions, attach the debugger to the sandboxed solution worker
process, SPUCWorkerProcess.exe and debug it.
9. Farm Solutions
• They're deployed by a farm administrator and are scoped
to the farm level.
• Also known as full trust solutions.
• They have full trust access to all resources and functionality
in SharePoint and, when deployed, require you to IISReset.
• Solution should deployed on both WFE’s and Application
Servers.
11. Deployment Items
• Visual Web parts
• Master Pages
• Content Types
• List Definitions
• Page Layouts
• User Controls
• Web Controls
• Site Definitions
21. Deployment Steps
Fresh Deployment
1. Adding Solution (*.wsp file)
Just add this solution to the SharePoint solution gallery (Site Collection/Farm Level)
2. Deploying Solution (*.wsp file)
Placed all the files present in the solution package will be deployed to their respective places.
User control files (.ascx) are copied to “%ProgramFiles%Common FilesMicrosoft Sharedweb server
extensions14TEMPLATEControlTemplates” or a subfolder of it.
Assemblies are deployed to the global assembly cache or to a web application's bin folder
Features are copied to a subfolder of “%ProgramFiles%Common FilesMicrosoft Sharedweb server
extensions14TEMPLATEFEATURES” and installed in the Feature Gallery of the farm, web application, site collection, or
website, depending on the scope of the Feature
3. Activation the Features
Activate the Features as required
Features must be activated before they can be used.
22. Deployment Steps
Upgrade Deployment
Deploy Solution v/s Upgrade Solution Concept
• Upgrade Solution If you rename the solution file or change the GUID, "upgradesolution"
operation will fail with an error stating that a solution with name or GUID does not exists in
solution store. But in case of “deploy solution” it will allow you to rename it.
• Deploy Solution When you deploy a solution and then their associated features are also
installed but that's not the case with "upgradesolution" operation. If you uninstall the features
and then upgrade the solution, it will not install the features. But if you deploy the solution it
will install the features again.
23. Deployment Steps
Upgrade Deployment (Deploy Solution Technique)
1. Disable and Uninstall all the Features
For the safe side you need to deactivate/disable the feature and then uninstall it .
2. Retracting Solution (*.wsp file)
Retracted solutions are not removed from the farm's solution store and can remain stored there in an un-deployed state indefinitely.
It will uninstall all the features which exists in the solution package.
3. Deleting Solution
Deleting the existing solution.
3. Adding Solution
Adding the updated solution in to the SharePoint solution store.
3. Deploying Solution
Deploying the newly added solution/package file. Will automatically installing the features and placed the files in to their respective places.
3. Activating Features
Activate the newly installed features as required.
24. Deployment Steps
Upgrade Deployment (Upgrade Solution Technique)
1. Upgrade Solution Package
Just performs upgrade operations on the Solution/Package file.
25. Deployment Steps
Upinstall Deployment
1. Disable and Uninstall all the Features
You must first need to deactivate/disable all the features and then uninstall it.
2. Retracting Solution (*.wsp file)
Retracted solutions are not removed from the farm's solution store and can remain stored there in an un-
deployed state indefinitely.
It will uninstall all the features which exists in the solution package.
3. Deleting Solution
Deleting the existing solution.
26. Deployment Approaches
• Two types of Deployment Approaches.
Use STSADM Command Line Tool
Use Power Shell Commands
27. STSADM Command Line Tool
• An .exe file “Stsadm.exe” resides in 14 hive Bin
folder.
Path: C:ProgramFilesCommonFilesMicrosoft
Sharedweb server extensions14BINstsadm.exe
28. STSADM Command Line Tool
Adding Solution
stsadm.exe -o addsolution -filename "DummySharePointProject.wsp”
* Perform Administrative Command
Deploying Solution
stsadm.exe -o deploysolution -name "DummySharePointProject.wsp" -allowGacDeployment -immediate –force
* Perform Administrative Command
stsadm.exe -o deploysolution -name "DummySharePointProject.wsp" -allowGacDeployment -immediate -force –allcontenturls
* Perform Administrative Command
Note: * Always perform this command after every command that need to run the administrative job.
* stsadm.exe -o execadmsvcjobs
29. STSADM Command Line Tool
Retracting Solution
stsadm.exe -o retractsolution -name "DummySharePointProject.wsp" -immediate
* Perform Administrative Command
stsadm.exe -o retractsolution -name "DummySharePointProject.wsp" -allcontenturls -immediate
* Perform Administrative Command
Deleting Solution
stsadm.exe -o deletesolution -name "DummySharePointProject.wsp"
* Perform Administrative Command
Note: * Always perform this command after every command that need to run the administrative job.
* stsadm.exe -o execadmsvcjobs
31. STSADM Command Line Tool
Deactivate/Disable Feature
stsadm.exe -o deactivatefeature -id [Feature ID] -url [TargetUrl] –force
Activate/Enable Feature
stsadm.exe -o activatefeature -id [Feature ID] -url [TargetUrl] -force
* [Feature ID] = Example: 4c9e8ca5-d893-42b8-a3b3-cae4b18bf133
* [TargetUrl] = provide the site URL from where feature is going to disabled.
http://mydummysiteserver:port/testsite
32. Power Shell Commands
Most Power full deployment tool
Have large number of command supports (Getter/Setter) available for commands
Can code normal C# code inside power shell script
Can execute our multiple commands through scripting logic
![SharePoint 2010
Session - 3
By: Usman Zafar Malik
[MCTS: MOSS 2007], [MSCBSS: CRM 3.0 / 4.0], MCP](https://image.slidesharecdn.com/sharepoint2010session3-120106133806-phpapp02/85/sharepoint-2010-training-session-3-1-320.jpg)
