Developing a provider hosted share point app


Published on

This talk was presented at SharePoint Saturday Austin in Texas on March 2nd, 2013.

  • 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

Developing a provider hosted share point app

  1. 1. DEVELOPING APROVIDER HOSTEDSHAREPOINT APPTalbott CrowellSharePoint Saturday AustinMarch 2nd, 2013
  2. 2. About Me•• Solutions Architect at ThirdM• A Founder of SharePoint Saturday Boston• Microsoft MVP• Blogger and Author
  3. 3. About this Talk• For Developers • Who want to build Apps For SharePoint• For Architects • Who want to understand options and architecture considerations of a Provider Hosted App• For Anyone • Who wants to learn more about SharePoint 2013 and the future of Extending and Customizing SharePoint
  4. 4. What is a Provider Hosted App• SharePoint 2013 Compatible Application• Hosted outside of SharePoint • Azure • Amazon Web Services (AWS) • Rackspace • Your Datacenter • An on-premise server in your customer’s Datacenter (you provide the Application, Hardware, and/or VM)• Written in any language on any platform • Java, F#, Ruby, Linux, Unix
  5. 5. App Development History • SharePoint 2003 – Web Parts • SharePoint 2007 – Farm Solutions & SPD • WSP (A CAB file with deployment assets and instructions) which may include: • Server Code (.NET Assemblies for GAC or BIN) • Client Code (JavaScript Files, CSS, HTML) • ASP.NET (ASPX, ASCX, Master Pages), Images, Site templates, List definitions, Content Types (CAML), Layouts, various other types of content • SPD (SharePoint Designer) • Create custom solutions with Workflows, JavaScript, HTML, jQuery, Master Pages, Layouts stored in Content Database • SharePoint 2010 • Sandbox Solutions • SharePoint 2013 • Apps for SharePoint
  6. 6. Apps for SharePoint Hosting Options• Provider Hosted Apps • SharePoint 2013 on-premise or Office 365 • Unlimited scaling• Autohosted Apps • Typically Azure Web Sites written in .NET • Runs only in Office 365 (no on-premise option) • Uses the consumers Office 365 Azure resources• SharePoint Hosted Apps • Client side only (JavaScript, jQuery, HTML, CS S) • Uses CSOM to manipulate SharePoint object•
  7. 7. Provider Hosted Apps Office 365 Data Center Application Runtime and Backendor On-Premise SharePoint 2013 Farm (Can be anywhere: On-Premise or Cloud) Provider SharePoint Provider 2013 Hosted Service app Provider Data Customer Provider
  8. 8. Alternative Using Autohosted Office 365 Data Center Application Runtime and Backend (including Azure) (Cloud Service you Host) Office 365 Autohosted app Provider(SharePoint Windows Azure Online) Service Azure Database Customer Data Provider Data Customer Provider
  9. 9. Provider Hosted Architecture• Store or App Catalog – Deployment Manifest .APP file• App Manifest – Declare App Permission Requests• Trust Settings – User must “allow” or “trust” your app• Provider receives Request with Trust Token• Provider uses CSOM to call back to SharePoint using the Trust Token• SharePoint persists changes made by the Provider in the Content Database (just like SharePoint Designer)
  10. 10. Costs of Being a Provider• Need to maintain and cover hosting cost • But you can extend your app to other ecosystems outside of SharePoint • iPad, Facebook, Kindle, Salesforce• Changes will affect ALL customers • May need a versioning strategy for customers in Life Sciences (long validation lifecycle)
  11. 11. Benefits of Provider Hosted• Does not tax the SharePoint Farm’s resources as much as Farm Solution might• Update 1000’s of SharePoint Farms with one release update to the Provider• Centrally managed at the Provider’s location• Develop on any platform using any language leveraging your existing developer and infrastructure knowledge• Same App works on Office 365 and SharePoint 2013 on- premise
  12. 12. Development Model• Get Started using Azure and Office 365 Preview • Many Blog posts on getting started• Deploy your Provider Hosted app to your Provider (Azure, AWS, Rackspace, local server)• Deploy your .APP file to SharePoint
  13. 13. Development System Requirements• Visual Studio 2012 • On Premise Development Environment •• Office Developer Tools for Visual Studio 2012 •
  14. 14. Decisions• Office 365 or On-Premise? • If Office 365, Visual Studio 2012 • If On-Premise then build your SharePoint 2013 Dev Server • Windows Server 2012 or Windows Server 2008 R2 SP1 • •
  15. 15. App Packaging• Start with Visual Studio 2012 Project Template• .APP • Contains AppManifest.xml • Set Permission Requests for your App • Start Page • Client ID • App Icon Image File• You can unpack the .APP by renaming .ZIP
  16. 16. Demo• Using Visual Studio to create the App Manifest• Explore Contents
  17. 17. Security• Client Secret vs Certificate • Client Secret requires SharePoint is farm connected to ACS • Azure ACS (Access Control Service) • Office 365 is already connected to ACS• AppManifest.xml (.APP) • Contains permissions• OAuth • TokenHelper.cs (runs on the Provider) • Helps you manage requests for app tokens • If you are developing in another language you will need to implement this yourself
  18. 18. OAuth ExampleTokenHelper.TrustAllCertificates();string contextTokenString = TokenHelper.GetContextTokenFromRequest(Request);if (contextTokenString != null) { contextToken = TokenHelper.ReadAndValidateContextToken( contextTokenString, Request.Url.Authority); sharepointUrl = new Uri(Request.QueryString["SPHostUrl"]); accessToken = TokenHelper.GetAccessToken( contextToken, sharepointUrl.Authority).AccessToken; CSOM.CommandArgument = accessToken;}
  19. 19. CSOM• Client Side Object Model• Rich improvements over 2012• .NET version• JavaScript version•
  20. 20. CSOM Exampleprotected void CSOM_Click(object sender, EventArgs e) { string commandAccessToken = ((LinkButton)sender).CommandArgument; RetrieveWithCSOM(commandAccessToken); WebTitleLabel.Text = siteName; CurrentUserLabel.Text = currentUser; UserList.DataSource = listOfUsers; UserList.DataBind(); ListList.DataSource = listOfLists; ListList.DataBind();}
  21. 21. CSOM Example ClientContext clientContext = TokenHelper.GetClientContextWithAccessToken( sharepointUrl.ToString(), accessToken); //Load the properties for the web object. Web web = clientContext.Web; clientContext.Load(web); clientContext.ExecuteQuery(); //Get the site name. siteName = web.Title; //Get the current user. clientContext.Load(web.CurrentUser); clientContext.ExecuteQuery(); currentUser = clientContext.Web.CurrentUser.LoginName; //Load the lists from the Web object. ListCollection lists = web.Lists; clientContext.Load<ListCollection>(lists); clientContext.ExecuteQuery();
  22. 22. Scope of Access• What can you get to from CSOM?
  23. 23. Putting it all together• Generate Client ID and Client Secret • Generated by form on SharePoint Online • https://<your site>/_layouts/15/appregnew.aspx• APP Manifest and Icon packaged in .APP file • Includes Permission Requests • Includes Client ID • Deployed to SharePoint• Your app is deployed to Azure, etc… • ClientID and ClientSecret• Your app receives Token from SharePoint user request• Your app uses Token to call CSOM
  24. 24. Review• SharePoint has completely new Development Model• Leverage existing understanding with CSOM• Leverage existing other technology knowledge• Update many customers (or Farms) at once• Costs and Benefits of being a Provider• Security with OAuth• Package and Deploy to Store
  25. 25. Resources• My Blog for Slides, Questions, and Follow up information •• Pluralsight Videos by Andrew Connell • Over 12 hours of Video •• Microsoft MSDN Documentation •• CloudShare for developer and test hosting •
  26. 26. More Resources• Steve Fox’s Blog • Create a free Azure Web Site to develop Provider Hosted App • •• Chris Johnsons loosely typed thoughts… • Build a SharePoint Provider Hosted App in 5 mins •
  27. 27. Thanks to our Sponsors!
  28. 28. Thank You Developing a Provider Hosted SharePoint App Presented by Talbott Crowell Please fill out evaluations!