While its very true that SharePoint’s development model is firmly rooted in the .NET development world, at the same time SharePoint can be appear to be a completely alien beast to even the most experienced of .NET developers. In this session, John will introduce the fundamental practices that a .NET developer should understand about SharePoint and needs to follow when building custom solutions for the platform, whether its creating web parts or building complex workflows and Line of Business applications for deployment within a SharePoint farm.

2. WHAT IS SHAREPOINT?

3. Maybe you’ve heard it called…

4. Or…

5. Perhaps You’ve Seen…

6. Or…

7. Let’s simplify things… SharePoint is:
• Collaboration
• Search
• Content Aggregation
• Content Management
• Applications

8. What kind of Applications?
• Data Display
• Business Collaboration
• Line of Business Applications
• Business Intelligence
• Process Management
• Public Web Sites

9. .NET AND SHAREPOINT

10. They have a lot in common
• Architecture
• Infrastructure
• Security
• Deployment
• Web Parts, Fields, User Controls

11. Why SharePoint?

12. With SharePoint you get:
• Security
• Search
• Content Management
• Workflows
• Provisioning

13. TOOLS FOR SHAREPOINT’S
NUTS AND BOLTS

14. Visual Studio 2010
• Broad SharePoint Support
• Build web parts, templates,
workflow, and much more
• Package and deploy
• View live SharePoint sites
• TFS Integration
• Extensible

15. SharePoint Designer 2010
• “No Code” development
• Customize sites, lists, web parts
• Design workflow
• Edit pages
• Free

16. Debugging Tools
(and the IE Developer Toolbar)

17. Supplemental Tools
CKS:DEV
Visual Studio 2010 SharePoint Power Tools

18. Managed
Code
• Traditional SharePoint & .NET Development
• Compiled
• Runs Server-Side

19. Client-Side
Code
• Not compiled
• JavaScript
• Silverlight

20. SharePoint
Development
Gotchas

22. Beware of Greedy Objects
• SPSite
• SPWeb
Similar,
but different:
• SPList.Items

23. No Unsupported Changes!
• SharePoint
Root
…but its ok
sometimes
• SharePoint
Databases
NEVER!

25. Deployment Packaging
• Always deliver via Solution Packages
(WSP)
• Perfection = 3 files
– .WSP
– Deployment Script
– Retraction Script
• Avoid Backup/Restore or Export/Import
• Remember to address configuration

26. What’s a WSP?
• Cabinet file
• Contains:
– XML Files
• Manifest.xml
• Feature.xml
– Assemblies
– Other Files
• Master Pages
• Page Layouts
• User Controls
• Image Files
• Stylesheets

27. Keys to Successful WSP Deployment
• Where is it going?
– Sandbox?
– Large Env
(instrument your
code!)
• Temper your
expectations
• Test your
deployments!

28. TESTING

29. Compilation ≠ Testing

30. Three Critical
Testing Stages
• Unit Testing
• Deployment Testing
• System Testing

31. PROVEN PRACTICES

32. Have Development Standards
• Naming
• Source Control
• Labeling Code Files

33. Use Virtualization

34. Code the Right Way
• Don’t get fancy
• Don’t expect Full Privilege
• Dispose your objects
• Log errors & activity

35. Avoid Tunnel
Vision
• No perfect solutions
• No “One-Size Fits All”
• Heed warnings

36. Document Everything

37. Have you thanked your
administrator today?

38. Questions?
QUESTIONS?