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.

Introduction to SharePoint Developer


Published on

This presentation is an introduction to SharePoint development for .NET developers who have no knowledge of SharePoint. It was delivered at the Carolina Code Camp on Saturday, May 4th, 2013.

Published in: Technology
  • Be the first to comment

Introduction to SharePoint Developer

  1. 1. Introduction to SharePoint DevFor .NET Developers
  2. 2. Who am I?• Kelly D. Jones– SharePoint Architect for CHS– 15 years industry experience; 5+ SharePoint• My blog:• Twitter: @KellyDJones
  3. 3. Agenda• Reason for this talk• SharePoint Background Info• SharePoint Development Environment• SharePoint Development Tools• SharePoint Development Options• Further Learning Resources
  4. 4. Reason for this talk• SharePoint is Microsoft’s fastest growingserver product– 78% of Fortune 500 use it (April 2011)– 1 in 5 Information Workers have it• Last year’s SP Conference had 10kattendees• Serious skills shortage in the job market• “So, what do I need to get started?”
  5. 5. First, a little background2001SharePointPortal ServerSharePointTeam Sites(STS)2003SharePointPortal Server(SPS)WindowsSharePointServices(WSS) 2.02007MicrosoftOfficeSharePointServer(MOSS)WindowsSharePointServices(WSS) 3.02010SharePointServerSharePointFoundation2013SharePointServerSharePointFoundation“Platform”“Servers”
  6. 6. SharePoint Dev Environment• SharePoint 2007– Windows Server 2003, x86 or x64• SharePoint 2010 – x64 only– Windows 7– Windows Server• SharePoint 2013– Windows Server 2008 R2 SP1 x64– Windows Server 2012
  7. 7. Dev Env: Win7 Workstation• Pros:– Minimizes hardware requirements– User friendly OS (laptop support)• Cons:– Not full fidelity – less functional than SP onserver– Doesn’t match production OS– Uses workstation resources even when notneeded– SP2010 only
  8. 8. Dev Env: Server in data center• Pros:– Typically administered by a server team– Can fully match SP prod environment– Typically better hardware/performance• Cons:– Typically administered by a server team– Increased cost (server hardware $$)– May need to share with other devs
  9. 9. Dev Env: Local Virtual Machine• Pros:– Dev has complete control– Take advantage of VM snapshots, backups– Easily toggle between VM environments (2007, 2010,2013)• Cons:– Dev has complete control (requires admin skills)– Workstation hardware: CPU, RAM, Disk– Dev responsible for backups of VMs– Requires x64 host OS & x64 VM software(2010/2013)
  10. 10. Dev Env: VM in the Cloud• Pros:– Can be spun up quickly (• Less admin skills required to get started– Cost flexibility (pay for what you use)• Cons:– Requires internet connectivity and dependenton hosting company (aka: cloud cons)– May not integrate with corporate network(domain, source control, etc.)
  11. 11. Dev Env: What’s installed?• OS – smoother if you match SP wave• SQL Server• SharePoint• Office• Dev ToolsTip: match your production environment:OS, SP, SQL, and patch level (servicepacks, CU)
  12. 12. SharePoint Dev Tools• Web Browser• Office– Word, Excel, PowerPoint, Visio, Access• InfoPath• SharePoint Designer• Visual Studio
  13. 13. SP Dev Tool: Web Browser• Working with Lists and Libraries
  14. 14. SP Dev Tool: Web Browser• Working with Pages
  15. 15. SP Dev Tool: Web Browser
  16. 16. SP Dev Tool: Web Browserhttp://sp2010/sites/teamsite1/_vti_bin/listdata.svc/MobileAppBanners
  17. 17. SP Dev Tool: Office• Visio Services
  18. 18. SP Dev Tool: Office• Excel Services (REST API)http://{SERVER}/_vti_bin/excelrest.aspx/{SITE}/{DOCUMENT_LIBRARY}/{document.xslx}/model
  19. 19. SharePoint HierarchySPFarmSPWebApplicationSPSiteSPWebSPListSPListItemSPDatabase &SPContentDatabaseClasses
  20. 20. SP Dev Tool: InfoPath• InfoPath Designer – create/edit form• InfoPath Filler – fill out a form
  21. 21. SP Dev Tool: SP Designer• Manage pages– Design view 2007/2010, not 2013• Manage lists• Create workflows• Free download
  22. 22. SP Dev Tool: Visual Studio• Create SharePoint artifacts– lists, workflows, web parts, etc.• Create eventreceivers
  23. 23. SP Dev Tool: Visual Studio• Build process outputs .WSP (pronouncedWISP)• CAB file
  24. 24. SP Dev Tool: Visual Studio• APIs available:– Farm Solutions – traditional API– Sandbox Solutions (new in 2010, deprecatedin 2013)– Web Services – SOAP, REST– Client Object Model• JavaScript• .NET
  25. 25. Misc Dev Tools• On– WSP Builder (more so for 2007)– SharePoint Log Viewer– SharePoint Manager– CKSDev• PowerShell
  26. 26. Resources• VMs:– Microsoft Information Worker Demo 2010–• How to build a VM: “SharePoint 2010development environment build guide”– Critical Path guide recommended• MSDN / Technet
  27. 27. Thank you.Any questions?My blog: http://www.KellyDJones.comTwitter: @KellyDJones