Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Intro to SharePoint 2010 development for .NET developers


Published on

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.

Published in: Technology
  • Be the first to comment

Intro to SharePoint 2010 development for .NET developers

  2. 2. Maybe you’ve heard it called…
  3. 3. Or…
  4. 4. Perhaps You’ve Seen…
  5. 5. Or…
  6. 6. Let’s simplify things… SharePoint is:• Collaboration• Search• Content Aggregation• Content Management• Applications
  7. 7. What kind of Applications?• Data Display• Business Collaboration• Line of Business Applications• Business Intelligence• Process Management• Public Web Sites
  9. 9. They have a lot in common• Architecture• Infrastructure• Security• Deployment• Web Parts, Fields, User Controls
  10. 10. Why SharePoint?
  11. 11. With SharePoint you get:• Security• Search• Content Management• Workflows• Provisioning
  13. 13. Visual Studio 2010• Broad SharePoint Support• Build web parts, templates, workflow, and much more• Package and deploy• View live SharePoint sites• TFS Integration• Extensible
  14. 14. SharePoint Designer 2010• “No Code” development• Customize sites, lists, web parts• Design workflow• Edit pages• Free
  15. 15. Debugging Tools (and the IE Developer Toolbar)
  16. 16. Supplemental Tools CKS:DEVVisual Studio 2010 SharePoint Power Tools
  17. 17. Managed Code• Traditional SharePoint & .NET Development• Compiled• Runs Server-Side
  18. 18. Client-Side Code• Not compiled• JavaScript• Silverlight
  19. 19. SharePointDevelopment Gotchas
  20. 20. Beware of Greedy Objects• SPSite• SPWebSimilar,but different:• SPList.Items
  21. 21. No Unsupported Changes!• SharePoint Root…but its oksometimes• SharePoint DatabasesNEVER!
  22. 22. 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
  23. 23. 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
  24. 24. Keys to Successful WSP Deployment • Where is it going? – Sandbox? – Large Env (instrument your code!) • Temper your expectations • Test your deployments!
  25. 25. TESTING
  26. 26. Compilation ≠ Testing
  27. 27. Three Critical Testing Stages• Unit Testing• Deployment Testing• System Testing
  29. 29. Have Development Standards • Naming • Source Control • Labeling Code Files
  30. 30. Use Virtualization
  31. 31. Code the Right Way• Don’t get fancy• Don’t expect Full Privilege• Dispose your objects• Log errors & activity
  32. 32. Avoid Tunnel Vision• No perfect solutions• No “One-Size Fits All”• Heed warnings
  33. 33. Document Everything
  34. 34. Have you thanked your administrator today?
  35. 35. Questions?QUESTIONS?