SharePoint Cincy F5 Tornado SharePoint Development Overview


Published on

An overview of SharePoint 2010 and 2013 development for beginners.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Twitter
  • SharePoint Cincy F5 Tornado SharePoint Development Overview

    2. 2. #SPcincy2013 on• Open wireless access is available.• Feel free to Tweet (#SPcincy2013) and blog during thesession.
    3. 3. Thanks to our Platinum Sponsors#SPcincy2013 on
    4. 4. BIOPatrickTucker, Principal ConsultantMCT, MCTS, MCPD, MCITP, MCSD, MCAD, MCDBAEmail: ortuckersnet@live.comBlog: www.tuckersnet.comTwitter: @TuckersNetDeveloper, Architect,Trainer for over 14 yearsSharePoint since 2005Country when country wasn’t cool
    5. 5. ABOUT SDSSDS Custom SharePoint SolutionsAgile development and SharePoint coding experience tocreate an optimal solution for your unique SharePointapplication and integration needs.· Workflow & InfoPath Forms for Business Process Automation· SharePoint Reports & BI Integration· Portals & Collaboration· Content ManagementAgile Practices for proven faster delivery, higher quality, & increased business value.
    6. 6. WHO’STHIS FOR?It’s for you if you’re a … A .NET developer new to SharePoint? A developer from anotherbackground or language Non-developer who wants to learnmore Recent lottery winner willing to givesome cash to local instructorsNot for you if you’re a ... Experienced SharePoint developer IT Pro who thinks development is forthe nerds and the birds Confused attendee who wanderedinto the wrong classIf you’re a SharePoint 2010 dev looking for new stuff in 2013, sit near the back so you can sneak out easily
    7. 7. .NET AND SHAREPOINTunderstanding how the platform is put together
    8. 8. SHAREPOINT SITS ONTOP OF ASP.NETSharePoint is a platform thatsits on top of ASP.NETASP.NETWeb Forms, not MVCSP 2010 is built on .NET 3.5SP 2013 is built on .NET 4.5SharePoint brings its ownobjects to the party and its ownway of doing thingsSo SharePoint developers aredifferent from ASP.NETdevelopers
    9. 9. SHAREPOINT ARCHITECTUREFarmWebApplication 1SiteCollection 1HostWeb AppWebSiteListItemItemLibraryFileFileSiteCollection 2WebApplication 2
    10. 10. SHAREPOINT OBJECTS & DATAFarm (SPFarm) – single configuration databaseWeb Application (SPWebApplication) – think IIS web site, one or more content databasesSiteCollection (SPSite) – top level plus subsites, security boundary, in 1 content databaseSite (SPWeb) – sub site, container for lists and libraries (which are not equal to db tables)
    11. 11. SHAREPOINT DEPLOYMENTstarting at the finish line
    12. 12. WRAPPINGTHINGS UP Features wrap up things like web parts, timer jobs, etc. Solutions (.wsp files) are the units of deployment in SharePoint 2010 Apps are a new means of deployment in SharePoint 2013 (.app files) SharePoint Designer may also be used to deploy changes to pages, lists, librariesand workflows in both 2010 and 2013
    13. 13. FARM SOLUTIONSThese solutions are deployed tothe SharePoint farm by anadministrator and run with fulltrustGAC DeploymentStill possible with SharePoint2013
    14. 14. SANDBOX SOLUTIONSDeployed to a solution store bya site owner.A move toward limitedpermissions and resourcesProvides as subset of classesDeprecated but still around inSharePoint 2013
    15. 15. CLOUDOffice 365SharePoint hosted by Microsoft(Azure) or by third party hosterNot all clouds are the sameClient side code becomes key
    16. 16. HOW TO CREATE FORSHAREPOINTso what can we build?
    17. 17. ARTIFACTSDefinitionsSite, list, contenttypes, etc.Visual ComponentsWeb Parts, AppParts,Controls, etc.ProcessingWorkflows, eventreceivers, timer jobsExternalConnectionsBCS, External EventReceiversPagesApplication Pages,Master Pages, PageLayouts
    18. 18. DEFINITIONS XML Based Definitions of sites, lists, content types, features, etc. Deployed to the server via features and solutions 14 Hive and/or 15 Hive, depending on SharePoint version
    19. 19. WEB PARTS May be created as a web part or visual web part Added to web part pages in definitions or by users In SharePoint 2010, may be deployed to the sandbox
    20. 20. PROCESSING Workflows Two workflow platforms – 2010 and 2013 SharePoint 2013 supports either platform SharePoint Designer is a prime time tool for 2013 workflows Event Receivers Code that runs in response to a feature or list action Deployed as definition plus code Remote event receivers are available for SharePoint 2013 apps Timer Jobs Allows scheduling of server side code processes on the farm
    21. 21. PAGES Master Pages allow UI reuse, introduced with ASP.NET Application pages Page Layouts add a visual layer to a content type and provide templates SharePoint pages may also be created in the “Pages” or “Site Pages” libraries
    22. 22. SHAREPOINT 2013 APPSMSDN states “Apps for SharePoint are self-contained pieces offunctionality that extend the capabilities of a SharePointwebsite. An app may include SharePoint components such asa lists, workflows, and site pages, but it can also surface aremote web application and remote data in SharePoint.”
    23. 23. SHAREPOINT 2013 APP HOSTING – think Azure; server and client code OKProvider-hosted – think your own hosting environment;server and client code OKSharePoint-hosted – think Office 365, client code only
    24. 24. HOW TO TALK TOSHAREPOINTlanguages, apis and tools
    25. 25. TWO SHAREPOINT WORLDSSP2010•.NETDeveloperSP2013•WebStandardsDeveloper
    26. 26. STANDARDS - 2010 SharePoint 2010 Declarative – CAML, XML,XSLT Used to build reusable definitions Used to query the data hidden deep in SQL tables Server Side Programming .NET languages (C#,VB.NET, etc. used to build solutions) Client Side Programming Client Object Model limited / subset of classes JavaScript, jQuery, JSON, etc. Services ASMX,WCF, REST PowerShell
    27. 27. STANDARDS - 2013 SharePoint 2013 Declarative – CAML, XML,XSLT Apps Development – HTML 5, CSS 3, JavaScript Server Side Programming .NET languages (C#,VB.NET, etc. used to build solutions) Client Side Programming RichClient Side Object Model (CSOM) for managed code and JavaScript JavaScript, jQuery, JSON, etc. Services REST,OData, OAuth (ASMX is deprecated) PowerShell
    28. 28. APIS Server Side Object Model Useful for farm solutions or LINQ to Objects or LINQ to SharePoint Client Side Object Model CSOM (C#, JavaScript) jQuery, JavaScript libraries Web Services WCF entry point in 2010 – client.svc, listdata.svc (still around if needed) SharePoint 2013 – client.svc entry point extended with REST (_api in URL) REST and OData Mobile NewAPI forWindows Phone applications
    30. 30. FEELING DISORIENTEDYET?So apps or no apps?To the cloud or the cellar?Client side or server side?
    31. 31. WHAT TO BUILDSHAREPOINT WITHtools of the trade
    32. 32. TOOLS Visual Studio 2010 and 2012 SharePoint 2010 and 2013 templates, including 2013 Apps Visual Studio 2012 Update 2 is most current Need Microsoft Office DeveloperTools forVisual Studio 2012 SharePoint Designer SPD 2010 – a graphical designer and workflow editor SPD 2013 – a workflow designer and light admin tool LightSwitch A “light” development tool to build little or no code applications “Napa”Office 365 Development A web based development tool for SharePoint online apps Can deploy to SharePoint directly with .app files
    33. 33. PROJECTSSharePoint 2010 /VS 2010 or 2012 SharePoint 2013 /VS 2012
    34. 34. COOL FREE STUFF Free SharePoint 2013 Sample Pack (lots of code samples) Free Office 365 Developer Site Free SharePoint 2010 DeveloperTraining from Microsoft Free HTML 5, CSS and JavaScript course from Microsoft Free SharePoint 2010 Code Samples
    35. 35. •Remember to visit the exhibit hall.•Get to know your user groups to find out about localactivities and events in your area.•Make sure you stick around for the closing sessionand turn in your business cards to be eligible for theprize raffles.#SPcincy2013 on
    36. 36. #SPcincy2013 on Twitterwww.sharepointcincy.comPlease Support our Sponsors!
    37. 37. THANKYOU!patrick.tucker@sds-consulting.comtuckersnet@live.comBlog: www.tuckersnet.comTwitter: @TuckersNet