SharePoint Saturday Sacramento 2013 SharePoint Apps
Download as PPTX, PDFā¢0 likesā¢496 views
The document discusses the development and hosting of SharePoint apps, highlighting the shift to a new app model that eliminates custom server code for easier upgrades and lower development costs. It covers various hosting options, including SharePoint-hosted, provider-hosted, and auto-hosted apps, along with their benefits and limitations. Additionally, the document addresses permissions, security, and the deployment process for SharePoint apps while providing example code snippets for creating and managing apps.
SharePoint Saturday Sacramento 2013 SharePoint Apps
- 1. SACRAMENTO
- 2. SharePoint Apps in SharePoint 2013 Ryan Schouten @shrpntknight ITG
- 4. About Me Ryan Schouten Worked with SharePoint for 7 years I have experience with SharePoint 2003 ā 2013 I have worked with ASP.Net for 11 years MCPD Contact Information [email protected] @shrpntknight http://www.sharepointknight.com
- 5. Objectives ā¢ The Need ā¢ Benefits ā¢ Hosting Options ā¢ Limitations ā¢ New Functionality ā¢ Development Options ā¢ Permissions and Security ā¢ Deployment ā¢ Break it Down
- 7. Hence the new App Model ā¢ No custom code on the SharePoint server ā¢ Easier to upgrade to future versions of SharePoint ā¢ Works in Office 365 SharePoint Online without limitations ā¢ Reduces the ramp-up time for those building apps ā¢ Donāt need to know/be as familiar with SharePoint ā-ismsā ā¢ Leverage hosting platform features in new apps ā¢ Enables taking SharePoint apps to different levels ā further than what can be done with farm / sandbox solutions
- 8. Benefits (continued) ā¢ Low cost of entry for developers ā¢ Hosted SharePoint Dev sites ā¢ No need to have a farm per developer (Shared Development Farms/Tenants) ā¢ No Intensive development environment requirements
- 9. Hosting Options SharePoint-Hosted App Provision an isolated sub web on a parent web (separate domain) ā¢ Reuse web elements (lists, files, out-of-box web parts) ā¢ No server code allowed; use client JavaScript for logic, UX Provider-Hosted App āBring your own server hosting infrastructure and technology platformā Get remote events from SharePoint Use CSOM/REST + OAuth to work with SP Cloud-based Apps Your Hosted Site Autohosted App Windows Azure + SQL Azure provisioned invisibly as apps are installed Azure SharePoint Host Web App Web* (separate SharePoint domain) SharePoint Host Web App Web* (separate SharePoint domain) SharePoint Host Web App Web (separate SharePoint domain)
- 10. Hosting Comparison SharePoint Hosted Cloud Hosted App Scope SharePoint Site Site or Tenancy Architecture Web Site Can be Multi-Tenant App Developer Skillset SharePoint + HTML/JS Full Stack UI Technologies SharePoint + HTML/JS Any Web Stack Server Code None Any Storage Lists and Libraries Any Key Limitations No Server Code Hosting Expertise Required Good forā¦ Smaller apps & resource storage Any type of Application
- 11. App Presentation Options Shape Description Example Immersive Full Page App App that implements a new scenario for customers Resource Tracking, Budgeting App Part Provides new parts you can add to your sites Weather, News, Stock Ticker Extension App Add new actions for documents and items Display Document Visualization, Print to Print Service Vendor
- 12. Limitations ā¢ Apps in general ā¢ Deployed to different domain(extra login possible) ā¢ Initial configuration is a pain ā¢ App Parts ā¢ Loaded in an iframe(size is fixed) ā¢ Also loaded from other domain
- 13. New Functionality ā¢ Improved CSOM ā¢ Improved Rest API ā¢ Needed since code is not run in SharePoint Processes ā¢ O-Auth Security ā¢ New Security Model to allow app specific permissions
- 14. Letās Create Our First App
- 15. JSOM Library ā¢ Library has two versions ā¢ PS.js ā minified version of the library ā¢ PS.Debug.js ā unminified with intellisense ā¢ Both can be found in the layouts folder ā¢ %ProgramFiles%Common FilesMicrosoft SharedWeb Server Extensions15TEMPLATELAYOUTS ā¢ http://siteurl/_layouts/15 ā¢ Easiest way to reference it in SharePoint is <SharePoint:ScriptLink name="PS.js" runat="server" ondemand="false" localizable="false" loadafterui="true" />
- 16. Example SP.SOD.executeOrDelayUntilScriptLoaded(GetProjects, "PS.js"); function GetProjects() { var projContext = PS.ProjectContext.get_current(); projects = projContext.get_projects(); projContext.load(projects, 'Include(Name, CreatedDate, Id)'); projContext.executeQueryAsync(onQuerySucceeded, onQueryFailed); }
- 17. Continued function onQuerySucceeded(sender, args) { var projectEnumerator = projects.getEnumerator(); while (projectEnumerator.moveNext()) { var project = projectEnumerator.get_current(); var row = tblProjects.insertRow(); row.insertCell().innerText = project.get_name(); row.insertCell().innerText = project.get_createdDate(); row.insertCell().innerText = project.get_id(); } }
- 18. Letās Try It
- 19. Permissions and Security ā¢ Apps have their own permissions ā¢ You must specify what SharePoint you want to access in your Manifest ā¢ Content is secured through Oauth ā¢ Users must have the permissions you need for them to install
- 20. Deployment ā¢ Everything Packaged into a .app file ā¢ This can be used to add the app manually to a site or publish it to the SharePoint Store
- 21. Letās Examine How this works
- 22. Gotchas ā¢ On-Premise Sites are not configured by default to handle Apps ā¢ Sideloading of apps is not enabled on this site. ā¢ Enable-SPFeature e374875e-06b6-11e0-b0fa-57f5dfd72085 ā url http://sp.contoso.com ā¢ App Management Shared Service Proxy is not installed. ā¢ Technet article on how to setup On-Premise for development ā¢ http://msdn.microsoft.com/en-us/library/fp179923.aspx
- 24. Join us right after at The Blue Prynt Socialize and unwind after our day of learning. Blue Prynt Restaurant & Bar 815 11th St, Sacramento, CA 95814 bluepryntsacramento.com SACRAMENTO