SharePoint development evolution from classic to app

  • 614 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
614
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
14
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • http://msdn.microsoft.com/en-us/library/sharepoint/jj163114.aspx
  • http://msdn.microsoft.com/en-us/library/sharepoint/jj164060.aspx
  • The following table provides guidance on which set of APIs to use for a selected list of common SharePoint extensibility projects. The remaining sections of this topic describe the various sets of APIs. Short for Linux, Apache, MySQL and PHP, LAMP is an open-source Web development platformhttp://msdn.microsoft.com/en-us/library/sharepoint/jj164060.aspx
  • Timer jobs are not possible within an app – within a SharePoint-hosted app, it’s difficult to see how any “scheduled processing” could ever be implemented. This is a key difference to an Azure or externally-hosted app (or single app component), which could either use the Azure Service Bus or even a scheduled task on a non-SharePoint server which calls into SharePoint using a client APIhttp://www.sharepointnutsandbolts.com/2012/08/sharepoint-2013-appsarchitecture.html
  • Questoperché le App: - non hanno la possibilità di eseguirecodice server-side su SharePoint (quindi non hanno la possibilità di utilizzareilclassico server object model), - hanno come scope solo ilpropriosito (l'AppWeb di cui parlavamoneiprecedenti post), - non hannoalcuntipo di accesso al sito padre o ad altrisitinellagerarchia, altre site collection o altre web application (questo è vero in parte, perchè con il Client Object Model per Javascript ad oggisiriesce ad accedere al sito padre, ma credo chetoglierannoquestapossibilità) - non possonoquindiinstallaresulsito padre le nostrepersonalizzazioni (vedi master page, page layouts, ecc..), - non possonoutilizzaretutte le tipologie di personalizzazionichesiamoabituatiora ad utilizzareall'internodellenostresoluzioni SharePoint 2010, ma ne possonoutilizzare solo una parte (vedremonelprossimo post la lista di quelledisponibili) - non hanno la possibilità per l'utente finale di interagire con ilcontenutodell'AppWeb (per capirci, non c'èpossibilità di entrare in "visualizzatuttoilcontenuto"; a liste e document library siperò) o di permettere la visualizzazione di tale contenuto dal sito padre.http://www.peppedotnet.it/Blog/SharePoint2013NewAppModelPart3.aspx
  • IIS site not reachableRemote event thrown an error
  • http://blogs.msdn.com/b/richard_dizeregas_blog/archive/2013/04/04/self-service-site-provisioning-using-apps-for-sharepoint-2013.aspx
  • http://www.sharepointnutsandbolts.com/2013/04/rolling-out-sharepoint-2013-apps-to.html
  • Neil Hodgkinson (MSFT). Neil is a specialist in Search on O365 and stated that Microsoft are cautious to release it just yet as they cannot anticipate the workload it will generate on the SharePoint Online infrastructure. They are currently conducting stress testing and are hoping to release the feature later this year if all goes well.Alternativeshttp://blogs.msdn.com/b/richard_dizeregas_blog/archive/2013/04/01/cross-site-publishing-alternatives-in-sharepoint-online-office-365.aspxAPPThe content search web part could be re-written for delivery through the app model as an “App Part” for SharePoint OnlineBecause an app part is delivered through a glorified IFRAME, it would be challenging to navigate to a new page from within the app part.  A link within the app would only navigate within the IFRAME (not the parent of the IFRAME).  Secondly, there isn’t a great mechanism for templating a site to automatically leverage an app part on its page(s).  REST API and Script Editor WebpartCombined with the new SharePoint REST APIs, the script editor web part can deliver mash-ups very similar to cross-site publishing and the content search web part.  Unlike apps for SharePoint, the script editor isn’t constrained by IFRAME containers, app permissions, or templating limitations.  In fact, a well-configured script editor web part could be exported and re-imported into the web part gallery for reuse.

Transcript

  • 1. 1 | SharePoint Saturday Milan – 18 May 2013
  • 2. Grazie ai nostri Sponsor! Silver Gold 2 | SharePoint Saturday Milan – 18 May 2013
  • 3. Marco Rizzi – Solution Architect – Avanade Italy marcorizzi@marcorizzi.com 3 | SharePoint Saturday Milan – 18 May 2013
  • 4. Old school      4 | SharePoint Saturday Milan – 18 May 2013
  • 5. WSP vs App           5 | SharePoint Saturday Milan – 18 May 2013
  • 6. Content of the section comes from msdn and technet 6 | SharePoint Saturday Milan – 18 May 2013
  • 7. Doing thinks the app way   7 7 | SharePoint Saturday Milan – 18 May 2013
  • 8. App development      8  8 | SharePoint Saturday Milan – 18 May 2013
  • 9. App development     9 9 | SharePoint Saturday Milan – 18 May 2013
  • 10. App object model         10 ASP.NET (asmx) web services Procedure Calls (RPC) calls to the owssvr.dll direct Remote 10 | SharePoint Saturday Milan – 18 May 2013
  • 11. Factors to determine API to use If you want to do this ... Create an ASP.NET web app that performs CRUD operations across a firewall on SharePoint data or external data that is surfaced in SharePoint by a BCS external content type JavaScript client object model Create an ASP.NET web app that performs CRUD operations on SharePoint data or external data that is surfaced in SharePoint by a BCS external content type, but does not have to call SharePoint across a firewall .NET Framework client object model, Silverlight client object model, or REST/OData endpoints Create a LAMP web app that performs CRUD operations on SharePoint data or external data that is surfaced in SharePoint by a BCS external content type REST/OData endpoints Create a Windows Phone app that performs CRUD operations on SharePoint data Mobile client object model Create a Windows Phone app that uses the Microsoft Push Notification Service to alert the mobile device of events in SharePoint Mobile client object model and the server object model Create an iOS or Android app that performs CRUD operations on SharePoint data REST/OData endpoints Create a .NET Framework application that performs CRUD operations on SharePoint data .NET Framework client object model Create a Silverlight application that performs CRUD operations on SharePoint data Silverlight client object model Create an HTML/JavaScript application that performs CRUD operations on SharePoint data JavaScript client object model Create an app for Office that works with SharePoint JavaScript client object model Create a custom Windows PowerShell command Server object model Create a timer job Server object model Create an extension of Central Administration 11 ... use these APIs Server object model Create consistent branding across an entire SharePoint farm Server object model Create a custom Web Part, application page, or ASP.NET user control Server object model 11 | SharePoint Saturday Milan – 18 May 2013
  • 12. Doing thinks the app way If you want the functionality of ... ... try these approaches. Custom Web Parts An app for SharePoint can have remote pages that contain custom Web Parts. Another option is to expose a page from a remote web application in an app part on a SharePoint site page. The remote page can have essentially the same UI controls and functionality as a Web Part. For more information, see How to: Create app parts to deploy with apps for SharePoint. Event receivers and Feature receivers An app for SharePoint can contain functionally equivalent remote event receivers. For more information, see Handling events in apps for SharePoint. Custom field (column) types An app can deploy a new field (column) that is based on one of the existing field types. The Calculated and Computed field types are especially flexible. Another option is to present your data in a remote web page with customized controls or grids. Custom web services built on the SharePoint Service Application Framework You can develop your custom web services as remote services. Application pages An app for SharePoint can include remote web pages that are available from every website on which the app is installed. An app can also use any of the built-in SharePoint Web Parts on site pages. 12 12 | SharePoint Saturday Milan – 18 May 2013
  • 13. Doing thinks the app way       13 | SharePoint Saturday Milan – 18 May 2013
  • 14. 14 | SharePoint Saturday Milan – 18 May 2013
  • 15. Shift to cloud ready      15   15 | SharePoint Saturday Milan – 18 May 2013
  • 16. Description 16 | SharePoint Saturday Milan – 18 May 2013
  • 17. App by Chris O'Brien    17 | SharePoint Saturday Milan – 18 May 2013
  • 18. App by Peppe.Net     18 | SharePoint Saturday Milan – 18 May 2013
  • 19. App in the Enterprise    19 | SharePoint Saturday Milan – 18 May 2013
  • 20. Description 20 | SharePoint Saturday Milan – 18 May 2013
  • 21. Provisioning what?        21 | SharePoint Saturday Milan – 18 May 2013
  • 22. Provisioning tasks          22   22 | SharePoint Saturday Milan – 18 May 2013
  • 23. 23 | SharePoint Saturday Milan – 18 May 2013
  • 24. Provision sites with app  24 | SharePoint Saturday Milan – 18 May 2013
  • 25. Provision sites with app  25 | SharePoint Saturday Milan – 18 May 2013
  • 26. Description 26 | SharePoint Saturday Milan – 18 May 2013
  • 27. App stapling       27 27 | SharePoint Saturday Milan – 18 May 2013
  • 28. App stapling - Internals    28 | SharePoint Saturday Milan – 18 May 2013
  • 29. App stapling Considerations     GetSPAppInstance  29 | SharePoint Saturday Milan – 18 May 2013
  • 30. Description 30 | SharePoint Saturday Milan – 18 May 2013
  • 31. App self executed      31 31 | SharePoint Saturday Milan – 18 May 2013
  • 32. App self executed       32 32 | SharePoint Saturday Milan – 18 May 2013
  • 33. 35 | SharePoint Saturday Milan – 18 May 2013
  • 34. An eye on the future       36 | SharePoint Saturday Milan – 18 May 2013
  • 35. 37 | SharePoint Saturday Milan – 18 May 2013
  • 36. Grazie 38 | SharePoint Saturday Milan – 18 May 2013