Deep Dive SharePoint 2013: Developing applications in SharePoint 2013: forget the past?


Published on

More info on

  • 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
  • Hello, welcome to this presentation on SharePoint 2013 presentation for developers; I hope that you enjoyed the TechDays so far.This presentation is the second presentation of SharePoint 2013; in the previous presentation danholmes ;In my presentation I will show you (with a lot of demos) what the most important topics that have been improved in SP2013 in the development point of view.
  • It is important to keep in mind that my presentation will be followed by 3 other presentation from LievenIliano There will be of course some overlaps, but Lieven will get deeper into some topics I’ve covered
  • The are plenty of new or improvedfeatures in SP2013 for devs : a new app model (->yesyoushouldalmostforgeteverything), a new featurecalled Client siderendering, wherejavascriptplays an important role, creating master pages nowiseasierwith a new toolcalled Design Manager, the client api has been improved and extended (both the CSOM and the REST), the sreversideobject model has also been improved, wecan have remotereceievers (eventhandlers), where web service willbeinvokedwhen a eventistriggered,Dsiplaytemplates, Jslink, a new workflow pltaformwhere SPD isking, youcancreate real & robustappswith Access 2013 and a new featurecalled Minimal downloadstartegythatimproves the user experience by downloadingonlywhat’snecessary on the SP page.
  • In SP2007 code (like web part) ran on the server; if the code wasbadlywritten the farmwas in danger; moving to anotherfarmwasverydangerousbecauseevery customisation has to betested.In SharePoint 2010 MS introduces SP in the cloud (aka SharePoint Online) as part of O365 and also the Client object model (CSOM and REST); to be able to run the customisation in the cloud (and in the cloud the farmwasshared), the code had to run in a veryprotectedenvironementcalled the sandbox : in the sandbox the functuonalitieswheremuch to limited and moreover the code ranwith the user permission (elevatedprivilegewas impossible).In SP2013 a new model call « App » isprovided, where no SP server side code runs in SP anymore; Client side code isused all the time; if server sideisusedit mus run in another (non SP) server like an server, php server etc…More details in Lieven session
  • 2 types of apps = SharePoint hostedapps : when the appsisinstalled in a SP web site a child site iscreated in SP just for the app; the appcan do whatevereitwants in hisinternal web site. Onlyjavascriptwillbeused; code caninteractwithsp by using CSOM or REST SP api.Cloud basedapp : code runs in another server2 variants :Provider hostedapp : youbringyourown application serverAutohosted : the server side code (including page thatwillbeloaded in SP Iframe) isprovided in Azure and isautomaticallycreatedbehind the curtain.More details in Lieven session
  • Apps mean « Store »There are 2 stores A public store : « marketplace »A corporate store: « appcatalo »A new service application thatwill manage the licences, the app monitoring, the permissionsMore details in Lieven session
  • Whatdoes an app looks like ?
  • Start Sharepoint ManagerGo to ict7\\contosoDemonstrate the partner web site show the corporate news appCreate an appfrom scratch & describeit, deployitmanually to the appcatalog (show the appcatalog)Show appwebswith SharePoint ManagerDeploy to catalog, explaincatalogIllustratecorporate news code
  • Create an Hello world app ->azure Access Service appExplaintokens p116 Contexttoken, Refreshtoken, Access Token, Authorizationtoken ?
  • Create a basic accessapp, on premise & O365
  • Wecancreateapps for SP, but wecanalsocreateapps for Office; thereis a new framework
  • Create a basic accessapp, on premise & O365
  • Microsoft has tremedouslyimprorved the workflow platform in SharePoint 2013.There are actually 2 workflow platforms : the old one (the one present in SP2010) isstillthere and allowyou to runyourold workflow if youwant.And you have the new one; thismeansthatwecan have 2 catgories of workflows in SP2013 : SP2010 workflows and SP2013 workflows. A wSP2013 workflow canstart a SP2010 workflow.
  • Let’s focus on the new platform : itiscalled Workflow Manager and isactually the workflow platformusedcreated for Azure, soitisveryscalable and robust.This platformrun on Premise, or if you running workflows in O365 your workflow willrun in on a platform on premise.As you notice, itis not part of SharePoint anymoren and the service bus manages the communication between the workflow manager and the sharepointfarm. There is a client side component call Workflow service manager.
  • The new platformallows new scalable topologies liketis one wherewe have several SharePoint famrs sharing a workflow farm in cluster.
  • Deep Dive SharePoint 2013: Developing applications in SharePoint 2013: forget the past?

    1. 1. Developing applications inSharePoint 2013: forget the past?Serge Luca
    2. 2. Who Am I ?Serge LucaSharePoint Business UnitManager @ICT7SharePoint MVPCo-author of 2 incoming books onSharePoint
    3. 3. Related sessions“Deep DiveSharePoint 2013: “Deep Dive “Deep DiveSharePoint App SharePoint 2013: SharePoint 2013:development Accessing SharePoint AppFundamentals “ SharePoint data “ Security”
    4. 4. What’s new for developers in SP 2013
    5. 5. AgendaApps for Apps forSharePoint Office JS Link WCM WorkflowsConclusions
    6. 6. Apps for SharePoint
    7. 7. Problems with custom code (Very) expensive upgrades to Stability new versions of SharePoint Code runs with the Do you really believe that identity/permissions of a sandboxed solution cannot specific user perform attacks ? The upgrade feature story is not clear for many dev (feature versioning or assembly versioning…)
    8. 8. Upgrading to a new version ofSharePoint ?
    9. 9. SharePoint App Model :past, present, future…
    10. 10. Apps Architecture Provider-Hosted App SharePoint Your Hosted WebCloud-based Apps “Bring your own server hosting infrastructure” SiteGet remote events fromSharePointUse CSOM/REST +OAuth to work with SP Autohosted App Windows SharePoint Azure Web Windows Azure + SQL Azure Websites provisioned invisibly as apps are installed SharePoint-Hosted App Parent Web Provision an isolated sub web on a parent App Web web • Reuse web elements (from (lists, files, out-of-box web parts) WSP) • No server code allowed; use client JavaScript for logic, UX
    11. 11. Apps lifecycle Catalogs Mngt Licences Mngt Tenants Mngt Perms Mngt Provider Monitor Apps hosted App External Web Site (IIS ?) Apps Service Application SP hosted App Authorized App Delegation *.app download Public app store Cloud Azure Web Site Auto hosted App Internal App *.app Promotion App Developer Site Web App #1 File System SharePoint Farm Cloud
    12. 12. Apps : UI experience Full page Fully Immersive (Mandatory) App Parts “Web Parts” (Optional) UI command extensions (Optional)
    13. 13. Communication betweenSharePoint and Apps OAuth Client Object Model (CSOM)/REST Pages (Clouded H App) Lists / Libs / Webs JavaScript Client Object Model (JSCOM) /REST Pages (SP Hosted App) Lists / Web Services Remote Event Receiver Libs Host web App web
    14. 14. What’s covered in the newCSOM/REST APIs?
    15. 15. SharePoint 2013 Remote API _api is new alias for _vti_bin/client.svc Server Client REST CSOM OData JSON JavaScript Silverlight .Net CLR Library Library Library Custom Client Code
    16. 16. REST or CSOM ?REST is not just for CRUDoperations anymore I use REST for cross platform code By default IBeware: (IOS/Androïd,…) stick to CSOMNO BCS NO managedmanipulation metadatawith REST manipulation
    17. 17. What you won’t be able to do with apps : Custom action groups & Custom custom Timer jobs definitions hidings User Delegate controls(.ascx) Controls
    18. 18. Apps for Office
    19. 19. New architecture, web based HTML5, Small footprint : JavaScript, CSS3, run in the in a secure appApps for office : XML, and REST browser (even in runtimejavascript api APIs Rich Client) environement
    20. 20. Office App Office Web AppTask Pane Excel Excel Word ProjectContent App Excel ExcelMail App Outlook Outlook
    21. 21. What is Napa ? Great way to start builing SharePoint & No need to All you need is Office apps in install Visual an Office 365 the web Studio Account
    22. 22. JavaScript everywhere(not just apps)
    23. 23. SharePoint Designer2010 2013 Data View Web Part was based JS Link replacesCould display Designing on XSLT -> No Designer  the Data ViewSharePoint Master Pages code too (except for Web Part (kindPages was possible complicated Workflows) of)
    24. 24. Can also be used in Custom fields :
    25. 25. Web Content Management
    26. 26. Majors WCM Improvements in SP2013
    27. 27. Designing Master PagesProblems in previous versions of SharePoint Pure DesignersMaster pages work (people) don’t want to The Designvery well, but much mess up with MANAGER is yourtoo complex SharePoint ! new friend 
    28. 28. Workflows
    29. 29. SharePoint 2013 Workflow Manager SharePoint 2010 SharePoint 2013 workflows workflows Windows Server SQL Server Windows Server SQL Server
    30. 30. SharePoint 2013 and Workflow Service Access Control SharePoint Events Content People Sharing 2010 WF SharePoint Designer 2013 Visual Studio 2012 OAuth _API (REST OM) Workflow Manager Workflow Services Manager Instances Interop Workflow Client Service Bus Deployment Messaging WF Service Application Proxy
    31. 31. Workflow topology SP Farm 1 Workflow Client Workflow Cluster SP Farm 2 • Each SP farm targets a different Workflow Manager scope Workflow Client
    32. 32. SharePoint Designer Workflows :new features
    33. 33. Conclusions
    34. 34. Key Takeaways Create Apps cannot Focus on the Apps, includin do everything client api g Office Apps WCM Javascript is everywhere Improvements New workflow platform : SPD is king
    35. 35. Thank You !