1. Customising SharePoint the supported way:
From end-user to admin interfaces
Chris O’Brien
cScape
http://sharepointnutsandbolts.blogspot.com

2. Introduction
• The problem:
– Modifying SharePoint - within support boundaries
– Typically should not modify existing files in 12 hive
(service packs/hotfixes could overwrite)
• Potential trouble spots:
– Templates for new sites
– Modifying authoring/admin interfaces
– SharePoint’s user controls

3. Introduction
• The solution techniques:-
– Custom site definitions
– Modify copies of original files
– CustomAction entries to modify links
– Delegate controls

4. Custom site definitions
• Good starting point for any SharePoint site
– Can ensure sites based on blank site for Content
Deployment (KB 923592)
– Can control default features/content
• Well-documented in WSS SDK
• Onet.xml file specifies functionality/content

5. demo
Custom site definitions

6. Customising admin interfaces
• Admin pages are just files on filesystem
– But not supported to modify them!
– Solution – modify a copy and redirect link
• With the feature framework we can:
– Deploy our customised file to 12 hive
– Add/redirect any links to this page in site admin
– Deactivate our customisation if required

7. Customising admin interfaces
• Common targets for links:
• Microsoft.SharePoint.SiteSettings (columns are named)
• Microsoft.SharePoint.Administration.Operations
• Microsoft.SharePoint.Administration.ApplicationManagement
(more later)
• Can add new categories for our links

8. demo
Customising admin interfaces

9. Customising admin interfaces (ctd)
• Other possible targets for links:
• Microsoft.SharePoint.ContentTypeTemplateSettings
• Microsoft.SharePoint.ContentTypeSettings
• Microsoft.SharePoint.Administration.ApplicationCreated
• Office.Server.ServiceProvider.Administration (Shared
Services/SSP links)
• Microsoft.SharePoint.ListEdit.DocumentLibrary
• Microsoft.SharePoint.Workflows
• Microsoft.SharePoint.StandardMenu (SiteActions menu)
• Microsoft.SharePoint.Create
• Microsoft.SharePoint.ListEdit
• EditControlBlock

10. Delegate controls
• Tell SharePoint which control to load at run-time
– Use to override which user control to load
– Avoids modifying OOTB user controls
• OOTB page layouts use extensively
– Global links e.g. ‘My sites’
– Publishing console
– Page head controls
• Can use standard .Net controls in SharePoint!

11. Delegate controls
• Control to load can be user or server control
• Lowest sequence number wins
– MS default is ‘100’
• Can pass properties from markup
– Control you implement should walk control tree

12. demo
Delegate controls

13. Other customisations
• CQWP – if amending properties:
– export .webpart file
– rename
– import
• Publishing console/RTE:
– files provided for customisation in master page gallery
– referenced from filesystem files

14. Summary
• Assume direct file modification unsupported
• SharePoint has extremely flexible architecture
– Designed for modification
• Make use of techniques covered:
– Custom site definitions
– Modify copy of file and redirect link
– DelegateControls

15. Q&A
Thank you
mail: c.obrien@cscape.com
blog: http://sharepointnutsandbolts.blogspot.com