Your SlideShare is downloading. ×

Fly Buys website development using SharePoint 2007


Published on

Presentation delivered to the Wellington SharePoint User Group in January 2008. The session covered the experience developing a large internet site using SharePoint 2007.

Presentation delivered to the Wellington SharePoint User Group in January 2008. The session covered the experience developing a large internet site using SharePoint 2007.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


    January 2008
    Fly Buys Website
  • 2. Overview
    Project Overview:
    • The goal
    • 3. The solution
    • 4. Public vs. Publish
    • 5. MOSS customisation
    • 6. ASP.NET development
    • 7. Lists vs. SQL
    Development and Deployment
    • Development environment
    • 8. Deployment strategies
    • 9. Content deployment
  • Project Overview
  • 10. Project Overview
    • A rebuild of the existing site using MOSS
    • 11. Look and feel to match brand refresh
    • 12. Make it easy for the marketing team to manage content
    • 13. Encourage people to join the programme
    • 14. Encourage members to be more active in redeeming rewards, and in engaging with participants
    • 15. Provide an easy way for maintaining semi structured data, including rewards and participant information
  • Project Overview
    The Solution
    • Use Web Content Management features as a platform
    • 16. Build custom functionality using ASP.NET 2.0
    • 17. MOSS Lists for storing data
    • 18. SQL for searching and complex queries
    • 19. MOSS Solution deployment for releases
  • Project Overview
    Publishing site
    • Internal site for content authoring
    • 20. Windows authentication and Active Directory
    Public site
    • External site for public users
    • 21. Forms based authentication and custom membership provider
    • 22. Content deployment to move content between environments
  • Project Overview
    MOSS Customisation
    • Content types, page layouts, web parts created in Visual Studio and deployed using features
    • 23. Single master page for both publish and public sites
    • 24. SPSecurityTrimmedControl to filter content
  • Project Overview
    ASP.NET development
    • Join form, member screens, reward search
    • 25. Created user controls/web parts in Visual Studio and placed on pages within the site
    • 26. Custom membership provider using ASP.NET 2.0 to authenticate via web services
  • Project Overview
    Lists vs. SQL
    • WSS Lists provide versioning, approval
    • 27. MOSS provides content deployment
    • 28. SQL is faster and more scalable (especially over multiple lists)
    • 29. Combined solution used MOSS lists for authoring, and SQL for searching
  • Development and Deployment
  • 30. Development and Deployment
    • Development – Ideally each developer has their own dev image or environment where they can do their thing and bring them together in a common environment
    • 31. Test – IT environment, ability to test out service packs and do preliminary tests.
    • 32. UAT – Mirror of production. Releases can be verified and tested before going into production.
    • 33. Production – Locked down. No development access.
  • Development and Deployment
    Fly Buys development environment
    • Developers running MOSS locally
    • 34. All artefacts stored in TFS
    • 35. Custom code developed in Visual Studio 2005
    • 36. Layouts and Styles authored in SharePoint designer and copied into TFS for release
    • 37. Post build scripts to move files from Visual Studio into MOSS
  • Development and Deployment
    Deployment strategies
    • STSADM backup and restore – good for one off deployments
    • 38. STSADM export/import – good for moving sites
    • 39. Content Deployment via Central Admin – good for scheduled deployments
    • 40. Content migration API – also good for scheduled deployments, more
    • 41. Features/Solution
  • Development and Deployment
    Features/Solution deployment
    Good for:
    Iterative development/deployment
    Deployment of assemblies and filesystem files (none of the other methods deal with this)
    Ability to deploy assemblies/filesystem files to all servers in a farm with Solution packages
    Possibilities for continuous integration
    Developer is responsible for evaluating and deploying dependencies (e.g. underlying content types).
    Updates to content types, list definitions, site columns etc. deployed via a Feature  must be done with the API - modifying original Feature files and then reprovisioning is not supported
    Can be very time-consuming due to lack of assistance from current tools
  • 42. Development and Deployment
    Deployment Demo
  • 43. Resources
    Ari’s blog –
    Chris O’Brien –
    Joel Oleson –