My slides from the session on SharePoint Saturday Belgium 2014

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ć

5. SharePoint code should be...

7. Deployment structure
Code structure
Source code management
Unit testing SharePoint
Agenda for today
Maintainable
Testable

9. Deployment structure

10. Monolithic WSP
Simpler Retraction of one WSP
removes shared libraries
from BIN/GAC
Only one version path
for components
Not granular enough
MySolution.wsp

11. Shared WSP + Feature WSPs
Functionality can be
separately versioned
and managed
Retracting one
functionality doesn’t
break shared libraries
More complex
Limited reusability

12. MySolution.Specific1.wsp
MySolution.Common.wsp
MySolution.Specific2.wsp
Shared WSP + Feature WSPs

13. Framework + Shared + Feature
WSPsCommon SharePoint
code can be versioned
separately
More control over code
reuse and management
over multiple solutions
Even more complex

14. MySolution1.Specific1.wsp
MySolution1.Common.wsp
MySolution1.Specific2.wsp
MyFramework.wsp
MySolution2.Specific1.wsp
MySolution2.Common.wsp
MySolution2.Specific2.wsp
Framework + Shared + Feature
WSPs

15. Custom services

17. Code structure

18. SharePoint project only

19. SharePoint + Library project

20. SharePoint + Multiple library projects

21. Multiple solutions

22. Demo: Simple to
Complex

24. Source code management
 •

25. Source code management
 •
“The Truth”
Developer 1
Developer 2
Developer 3
Developer 1
Developer 2
Build Server
Corporate
Repository

26. Branching

27. Single release branch

28. Two branches (dev + release)

29. Feature branches

31. Unit tests

32. Testing levels

33. Depends on abstractions
Separates concerns
Inversion of Control (IoC)
Dependency Injection (DI)
Repository pattern
Service Locator pattern
MVP/MVC
Testing-friendly code

34. Demo: Adding unit
testing

35. Testing strategies
coordinating code
concrete repositories
(the ones that hit SharePoint or a
database)
CUT

36. SharePoint “quirks” with unit testing

38. Maintainable, testable SharePoint

39. Dank jullie wel!
Merci beaucoup!
@ekapic
www.edinkapic.com