Maintainable Testable SharePoint Components SPSBE 2014
Upcoming SlideShare
Loading in...5
×
 

Maintainable Testable SharePoint Components SPSBE 2014

on

  • 315 views

My slides from the session on SharePoint Saturday Belgium 2014

My slides from the session on SharePoint Saturday Belgium 2014

Statistics

Views

Total Views
315
Views on SlideShare
312
Embed Views
3

Actions

Likes
0
Downloads
5
Comments
1

1 Embed 3

https://twitter.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Love your picture on SharePoint unit testing! ;-p
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Template may not be modified Twitter hashtag: #spsbe for all sessions
  • How Beezybranchesaredone

Maintainable Testable SharePoint Components SPSBE 2014 Maintainable Testable SharePoint Components SPSBE 2014 Presentation Transcript

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