Successfully reported this slideshow.
SHAREPOINT USER GROUP PRESENTATION<br />January 2008<br />Fly Buys Website<br />
Overview<br />Project Overview:<br /><ul><li> The goal
 The solution
 Public vs. Publish
 MOSS customisation
 ASP.NET development
 Lists vs. SQL</li></ul>Development and Deployment<br /><ul><li> Development environment
 Deployment strategies
 Content deployment</li></li></ul><li>Project Overview<br />
Project Overview<br />Goals<br /><ul><li> A rebuild of the existing site using MOSS
 Look and feel to match brand refresh
 Make it easy for the marketing team to manage content
 Encourage people to join the programme
 Encourage members to be more active in redeeming rewards, and in engaging with participants
 Provide an easy way for maintaining semi structured data, including rewards and participant information</li></li></ul><li...
 Build custom functionality using ASP.NET 2.0
 MOSS Lists for storing data
Upcoming SlideShare
Loading in …5
×

Fly Buys website development using SharePoint 2007

904 views

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Fly Buys website development using SharePoint 2007

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

×