Your SlideShare is downloading. ×
SharePoint Saturday Belgium 2014 Building maintainable testable SharePoint components
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SharePoint Saturday Belgium 2014 Building maintainable testable SharePoint components

111
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
111
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. How to Build Maintainable and Testable Custom SharePoint Components #SPSBE24 Edin Kapić April 26th, 2014
  • 2. Thanks to our sponsors! Gold Silver
  • 3. Beezy Catalonian SharePoint User Group sug.cat Ik vraag me af of dit bier compatibel is met SharePint @ekapic www.edinkapic.com Edin Kapić
  • 4. SharePoint code should be...
  • 5. Deployment structure Code structure Source code management Unit testing SharePoint Agenda for today Maintainable Testable
  • 6. Deployment structure
  • 7. Monolithic WSP Simpler Retraction of one WSP removes shared libraries from BIN/GAC Only one version path for components Not granular enough MySolution.wsp
  • 8. Shared WSP + Feature WSPs Functionality can be separately versioned and managed Retracting one functionality doesn’t break shared libraries More complex Limited reusability
  • 9. MySolution.Specific1.wsp MySolution.Common.wsp MySolution.Specific2.wsp Shared WSP + Feature WSPs
  • 10. Framework + Shared + Feature WSPs Common SharePoint code can be versioned separately More control over code reuse and management over multiple solutions Even more complex
  • 11. MySolution1.Specific1.wsp MySolution1.Common.wsp MySolution1.Specific2.wsp MyFramework.wsp MySolution2.Specific1.wsp MySolution2.Common.wsp MySolution2.Specific2.wsp Framework + Shared + Feature WSPs
  • 12. Custom services
  • 13. Code structure
  • 14. SharePoint project only
  • 15. SharePoint + Library project
  • 16. SharePoint + Multiple library projects
  • 17. Multiple solutions
  • 18. Demo: Simple to Complex
  • 19. Source code management  •
  • 20. Source code management  • “The Truth” Developer 1 Developer 2 Developer 3 Developer 1 Developer 2 Build Server Corporate Repository
  • 21. Branching
  • 22. Single release branch
  • 23. Two branches (dev + release)
  • 24. Feature branches
  • 25. Unit tests
  • 26. Testing levels
  • 27. Depends on abstractions Separates concerns Inversion of Control (IoC) Dependency Injection (DI) Repository pattern Service Locator pattern MVP/MVC Testing-friendly code
  • 28. Demo: Adding unit testing
  • 29. Testing strategies coordinating code concrete repositories (the ones that hit SharePoint or a database) CUT
  • 30. SharePoint “quirks” with unit testing
  • 31. Maintainable, testable SharePoint
  • 32. Dank jullie wel! Merci beaucoup! @ekapic www.edinkapic.com

×