Sustainable SharePoint 2010Customizations

By Bill Keys

Our Environment

● SharePoint 2010 Enterprise● Threat Management Gateway● Active Directory Integration● Production and Test Environments

● Two SharePoint servers and one database server for each environment

Challenges

● SSO with Third-party Applications● Supporting Multiple Computing

Environments● High Availability● Preparing for Next Version

Safe Guards

• Quotas• Recycle Bin• Backups• Max Upload – Protect our Database• Custom User Permissions

• No page deleting rights, no applying css, create groups, etc.

• Test environment – TEST TEST TEST!

Custom Development

Web Parts

● Content Editor Web Part● Custom HTML and JavaScript● <iframe>● Hidden Web Part for customization to local

CSSDemo

● Content Query Web Part● SharePoint list and CQWP is a great match!Demo

InfoPath FormBefore

After

SharePoint DesignerAdvantages Deployment is fast Build for SharePoint Rapid developmentDisadvantages

Server side code not supported Little software developers tools support

Usages Add HTML, CSS, JavaScript or JQuery to a page Workflows

Server Side Code

• Can’t developed on client side?• SSO Third Party Applications

• Trusted Keys• Get user profile information

• Need code to send email?

Using ASP.NET Code

• Inline code not support by default• <% Response.Write(“<b>Hello World</b>");%>• Need to edit web.config to allow

• Application Pages• Regular aspx pages• Usually reside in sub folder in_ layouts

Visual Studio comes to the rescue

Visual Studio● For Developers● Templates for SharePoint● Packaging● Deployment

VS Custom Development

Examples

• Daily Digest• SharePoint Lists and Forms• ASP.Net code to support sending email

• eColleage SSO• SharePoint User Profile• Code

Source Control

Now Supports Git!

Debugging• SharePoint Developer Dashboard

• Firebug• Fiddler – HTTP traffic debugger

SharePoint 2013

Prepare for migrating to SharePoint 2013•New App Model•XSLT replaced with JavaScript- based CSR•.Net 4.5 support•New Web Parts for customizations•Styling changes

2010 Solutions to 2013

• Import package into Visual Studio 2012• Edit your .cspro

• Build, package, deploy

2010 SPServices JQuery to 2013• Core of SPServices

works 2013.• DOM has changed• New CSS• Keep your 2010 code

clean and modular• Post to community

form

2013 Web PartsContent Editor

Content Query Improved

Best Practices

1. Don’t code if you don’t need too.2. Don’t manually make changes to config files3. Document all customizations4. Think future migrations

Thanks you!

Contact me at william.keys1@gmail.comhttps://github.com/billkeys