Approaches and Best Practices for deploying SharePoint sites

DEV212

Chris O’Brien - MVP

Ask The Experts Panel Text numbers 1. IT PRO – 07891 100640

2. DEV – 07790 108093

  3. IW – 07790 132855

  4. BA – 07989 359425

Chris O’Brien, MVP, MCSD.Net, MCTS

www.sharepointnutsandbolts.com

Hands-on developer Author of Content Deployment Wizard tool Regular speaker at UK user group

What we’ll cover

Deployment goals and challenges Options:

Deployment with Features STSADM export Content Deployment/Wizard Kivati Studio/code/PowerShell

Considerations Best practices and guidelines

The challenge

Most projects will use multiple environments (esp. WCM)

Complex mix of .Net/SharePoint artifacts Files/assemblies SharePoint schema (e.g. content types, site

columns) SharePoint content Configuration (e.g. web.config)

Deployment goals

Repeatable Should always be able to rebuild from zero

Predictable Acceptable packaging effort

Automation scale

Documentation is critical

Deployment options

Demo

FEATURES

Option 1: Features

Pros Classic approach for rolling out functionality

to multiple site collections Fairly rich framework/tools Can provision files as ‘uncustomized’

Cons Deals with schema only, not data Relatively steep learning curve Code often required for updates

Option 2: STSADM export

Pros Very simple Moves site collections/web – data & schema Can be scripted

Cons Doesn’t allow setting of certain switches All objects given new IDs – can break things

– ListView web parts, InfoPath connections etc.

Bi-directional can cause problems

Option 2: STSADM export

Other considerations: Is not backup/restore! Not deployed:

– Alerts– Audit trail– Change log history– Recycle bin items– Workflow tasks/state

Demo

CONTENT DEPLOYMENT WIZARD

Option 3: Content Deployment Wizard Pros

Same deal as STSADM export, but..– Exposes more switches e.g. retain IDs– Can deploy site collection/web/list/list item

Can be scripted (beta) Cons

Files are deployed as customized Bi-directional can cause problems Need to understand capabilities

Demo

KIVATI STUDIO

Option 4: Kivati Studio

Pros Packages updates into .exe for administrator

– Nice structure for e.g. content type updates

Workflow designer allowing reuse Can write custom code if no built-in task

Cons Fairly steep learning curve Potential lock-in? Doesn’t move content e.g. list items/files

Choosing a method

Choosing a method - factors

Features are generally the best option, but consider: Type of solution:

– Single site collection/WCM – Wizard good here– Multiple site collection

Packaging experience– Timeframe also a factor

Frequency/type of updates– More code required to update Features

Choosing a method – factors

If multiple developers, consider team dev model:

Best practices – to always do

Always use WSPs for file system files, SafeControl entries etc.

Document how to deploy/rebuild site!

Identify how updates will be rolled out E.g. Updates to content types, list schemas

etc.

Best practices – avoid:

Using STSADM backup/restore to move a site Only for restoring to same location!

Using ‘Save as site template’ to move a publishing site Not all settings saved

Modifying live Feature or site def files Update using code once deployed

Summary

Don’t lose sight of deployment goals We considered 4 approaches

Identify approach which suits project Analysed factors in decision

Some best practices are always relevant Documentation Need to avoid ‘pitfall’ methods!

Resources: Kivati – www.kivati.com Deployment Wizard –

www.codeplex.com/SPDeploymentWizard P & P/Rob Bogue - ‘Upgrading SharePoint

apps’ - http://www.thorprojects.com/blog/archive/2009/02/28/upgrading-your-sharepoint-applications.aspx

Thank you for attending!

Questions?