Elaine van Bergen

OBS

Architect

ConfigureChanging settings within the environment at a high level such as SharePoint Farm, Server or DB.

CustomiseModifying the environment without writing code that requires compilation

Code Modifying the environment through compiled code

System Administration SharePoint Administrators Site Administrators Developers

End Users

Function Dev (multiple)TestStaging*ProductionDR DesktopOthers

Web Front End Serves pages

DatabaseStores Content

IndexCrawling

Configure

6.

Get to know your system administrator and DBA

Changing settings, can easily break SharePoint

Generally not even be SharePoint specific, think database, office, security, internet explorer

Always use SharePoint UI’s for changing settings e.g. central administration not IIS

Consider the database as off limits until you have read the necessary white papers from Microsoft.

IT and the business need to work together on settings changes

9.

Ensure test strategy is defined

This needs to involve the key stakeholders and key business functions

Push changes through the test environment first

Avoid “This problem only happens on production”

Document

Script

Use a tool to synchronise

Customise

12.

Web parts

Content Types

Branding

Workflow

These are not as harmless as they sound

Content Queries – Large queries

XSLT – Incorrect syntax

RSS – Malicious feeds, internet access

Page Viewer – Malicious content

Consider what web parts are appropriate

Changes may not propagate as expected

Adding fields work well

Fields with the same display name

Fields with different internal names in locations

Rapid development is possible using tools like SharePoint designer

Changes may break the entire site

Think about different sorts of sitesMeeting workspaces Search

Back-up and rollback strategy

Move between system environments

How will this be tested

Loops, annoying test emails, deleting information

Deployment strategy

18.

Control using security and policy but need to preserve the goal

Educate the users

Provide a training playpen

Customisations should go via a test server too

Monitor the system

Have a backup and rollback strategy

Code

20.

Why are you writing code ?

Negotiate first, code second

Code sources:BuyDownloadDevelop

Do you have a support strategy ?

SharePoint code is just .Net code but has it’s own best practises

Traps for new players

Memory managementExcessive database round trippingForgetting about scale Forgetting about security

Frequent recycles of application pool, especially during peak usage

Application crashes that appear as heap corruption in the debugger

High memory use for Microsoft Internet Information Services (IIS) worker processes

Poor system and application performance

using(SPSite site = new SPSite("http://server")){using(SPWeb web = site.OpenWeb()){...}}

using( SPWeb web = SPControl.GetContextWeb(HttpContext.Current)) { ... }

using (SPWeb web = new SPSite(SPContext.Current.Web.Url).OpenWeb()) { ...}

But SPDispose check helps

Does will it work with the following: Large number of sites and lists 2000+ items in a folderMultiple web serversAlternative access mappings

Does it work for different usersReaderContributor

Create features and bundle into solution (WSP) to deploy

WSP’s automatically get deployed to all servers in the farm

WSP’s can do more than just deploy web parts and files

Staple your features if needed on site creation

27.

Packaging Coding standards SPDisposeCheckSupported/Upgradable

Load + Performance test Security testAccessibility

Questions ?

Elaine van Bergen

@laneyvb on twitter

http://laneyvb.blogspot.com

29.