Share Point Apps in Share Point 2013 Ryan

Share. Point Apps in Share. Point 2013 Ryan Schouten @shrpntknight ITG

Special Thanks to our Platinum Sponsor …and our Gold Sponsor

About Me Ryan Schouten Worked with Share. Point for 7 years I have experience with Share. Point 2003 – 2013 I have worked with ASP. Net for 11 years MCPD Contact Information Ryan. Schouten@itg-mail. com @shrpntknight http: //www. sharepointknight. com

Objectives • • • The Need Benefits Hosting Options Limitations New Functionality Development Options Permissions and Security Deployment Break it Down

Why the change

Hence the new App Model • No custom code on the Share. Point server – Easier to upgrade to future versions of Share. Point – Works in Office 365 Share. Point Online without limitations • Reduces the ramp-up time for those building apps – Don’t need to know/be as familiar with Share. Point “-isms” – Leverage hosting platform features in new apps • Enables taking Share. Point apps to different levels – further than what can be done with farm / sandbox solutions

Benefits (continued) • Low cost of entry for developers – Hosted Share. Point Dev sites – No need to have a farm per developer (Shared Development Farms/Tenants) – No Intensive development environment requirements

Hosting Options Cloud-based Apps Get remote events from Share. Point Use CSOM/REST + OAuth to work with SP Provider-Hosted App Share. Point Host Web “Bring your own server hosting infrastructure and technology platform” App Web* Autohosted App Windows Azure + SQL Azure provisioned invisibly as apps are installed Share. Point-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 Java. Script for logic, UX Your Hosted Site (separate Share. Point domain) Share. Point Host Web App Web* (separate Share. Point domain) Share. Point Host Web App Web (separate Share. Point domain) Azure

Hosting Comparison Share. Point Hosted Cloud Hosted Share. Point Site or Tenancy Web Site Can be Multi-Tenant App Developer Skillset Share. Point + HTML/JS Full Stack UI Technologies Share. Point + HTML/JS Any Web Stack None Any Lists and Libraries Any Key Limitations No Server Code Hosting Expertise Required Good for… Smaller apps & resource storage Any type of Application App Scope Architecture Server Code Storage

App Presentation Options Shape Description Example Immersive Full Page 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

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

New Functionality • Improved CSOM • Improved Rest API – Needed since code is not run in Share. Point Processes • O-Auth Security • New Security Model to allow app specific permissions

Let’s Create Our First App

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 – %Program. Files%Common FilesMicrosoft SharedWeb Server Extensions15TEMPLATELAYOUTS – http: //siteurl/_layouts/15 <Share. Point: Script. Link name="PS. js" runat="server" ondemand="false" localizable="false" loadafterui="true" /> • Easiest way to reference it in Share. Point is

Example SP. SOD. execute. Or. Delay. Until. Script. Loaded(Get. Projects, "PS. js"); function Get. Projects() { var proj. Context = PS. Project. Context. get_current(); projects = proj. Context. get_projects(); proj. Context. load(projects, 'Include(Name, Created. Date, Id)'); proj. Context. execute. Query. Async(on. Query. Succeeded, on. Query. Failed); }

Continued function on. Query. Succeeded(sender, args) { var project. Enumerator = projects. get. Enumerator(); while (project. Enumerator. move. Next()) { var project = project. Enumerator. get_current(); var row = tbl. Projects. insert. Row(); row. insert. Cell(). inner. Text = project. get_name(); row. insert. Cell(). inner. Text = project. get_created. Date(); row. insert. Cell(). inner. Text = project. get_id(); } }

Let’s Try It

Permissions and Security • Apps have their own permissions • You must specify what Share. Point you want to access in your Manifest • Content is secured through Oauth • Users must have the permissions you need for them to install

Deployment • Everything Packaged into a. app file • This can be used to add the app manually to a site or publish it to the Share. Point Store

Let’s Examine How this works

Gotchas • On-Premise Sites are not configured by default to handle Apps • Sideloading of apps is not enabled on this site. – Enable-SPFeature e 374875 e-06 b 6 -11 e 0 -b 0 fa-57 f 5 dfd 72085 – 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/fp 179923. aspx