In this session, I discuss and demonstrate how you can use SharePoint 2010 Web Templates and PowerShell scripts to give your team-based SharePoint development process a much needed productivity boost. Using these techniques, you enable your team to quickly test and review their custom components against your complete SharePoint solution while simultaneously eliminating inconsistencies often created by manual configurations. By the end of this session, you will have learned: How SharePoint web templates can be used to provision customized SharePoint sites How to leverage PowerShell scripts to automate your custom site build and feature deployments The key benefits of this approach for team-based SharePoint development So stop wasting time and come see how you can help make your SharePoint team development better, faster, and stronger!

1. Better, Faster, Stronger!
Boost Your Team-Based SharePoint Development Using
SharePoint 2010 Web Templates and PowerShell
Richard Calderon
Principal Consultant, Catapult Systems

2. 

www.catapultsystems.com

 richard.calderon@catapultsystems.com


2

3. More About Me
 Live in Austin, Texas
 Part-time musician
 Played the drums since I was a kid
 Studied music in college (Percussion Performance)
 Huge fan of Star Wars, saw all six movies in the theater 3

4. Web Templates – What are they and why should we use
them for provisioning SharePoint sites?
PowerShell – Automating site deployment during
development phase using PowerShell scripts
Key Benefits of this pattern for SharePoint
team-based development
4

5. Primary • Solution Architects
Audience • Development Project Leads
• SharePoint (.NET) Developers
Secondary
• SharePoint UI/UX Developers
Audience • SharePoint Administrators
5

6. 






6

7. 





7

8. Provision one
Create custom site
SharePoint web Enable SharePoint
columns and content
application and site Publishing features
types
collection
Provision list instances Apply custom Provision custom
based off of custom branding, including publishing pages
lists custom page layouts from page layouts
Set default (welcome)
Deploy a few custom
page and navigation
.NET component
options for each web
(web parts, etc.)
in the site collection
8

9. 


9

10. 1.


2.

3.


10

11. 





11

12. 12

14. Site Definitions Traditional WebTemp*.xml + onet.xml Changes to existing
combination, contains one or more site site definitions not
definition configurations supported by MS
Stored on file system of SharePoint Can only be deployed
server(s) in folder: using farm solutions,
%ProgramFiles%Common FilesMicrosoft so not an option for
Sharedweb server deployment to
extensions14TEMPLATESiteTemplates SharePoint Online
Site Templates* Created in the SharePoint UI by using an “Save site as template”
existing site as a model method not supported
by MS when publishing
“Save as site template” saves .wsp file to features are enabled
Solution Gallery of site collection (stored in
the content database)
Site Types: WebT atesand Site Definitions
empl
14

15. Feature Stapling Used to extend and customize Can only extend existing
existing site definitions site definitions, cannot
create new site “types”
Portal Replace onet.xml file with code + WebTemp*.xml files must
Provisioning WebTemp*.xml files be deployed to file system,
Providers so not an option for
deployment to SharePoint
Online
Custom code Typically used for automated site Can be used but is a non-
provisioning from existing site standard method
definitions or site templates
Web Templates New feature element available in SharePoint 2010
15

16. 


 16

17. 


17

18. 




18

19. 


 Community Kit for SharePoint

 CAML .NET Intellisense
19

20. 

 SharePoint 2010 and web
templates
20

21. 


Which
SharePoint 2010 Site
Template is Right for Me?
21

22. 1.
2.
3.
4.
22

23. 


23

24. 1.
2.
3.
24

25. 25

26. 

26

27. 




27

30. Project1/bin/Debug/ Package1.wsp
Deployment
Project2/bin/Debug/ Package2.wsp
Project3/bin/Debug/ Package3.wsp
30

31. 1.
31

32. 2.
copy $(TargetDir)$(TargetName).wsp $(SolutionDir)Deployment$(TargetName).wsp
3.
4.
32

33. 


33

36. 


36

37.  http://powergui.org
37

38. 







 38

39. 

39

42. 







 42

43. 



43

44. 



44

45. 


45

46. 
 http://blogs.msdn.com/b/vesku/

http://toddbaginski.com/blog/which-
sharepoint-2010-site-template-is-right-for-me/
46

47. 

http://technet.microsoft.com/en-
us/library/ee662539.aspx

http://www.microsoft.com/resources/TechNet/en-
us/Office/media/WindowsPowerShell/WindowsPowerShell
CommandBuilder.html
47

48. 
 http://powergui.org/downloads.jspa

http://cksdev.codeplex.com/

http://visualstudiogallery.msdn.microsoft.com/15055544-
fda0-42db-a603-6dc32ed26fde/

http://pbs2010.codeplex.com/
48

49. 
 http://www.slideshare.net/rcatx/using-web-templates-and-
powershell-to-improve-sharepoint-team-development-
12730158
49

50. Richard Calderon, Catapult Systems
Email: richard.calderon@catapultsystems.com
Twitter: @rcatx
LinkedIn: www.linkedin.com/in/rcatx
50