SharePoint 2013 Apps
•Download as PPTX, PDF•
3 likes•2,104 views
The document discusses SharePoint 2013 apps. It provides an agenda that covers an introduction to apps, comparing apps to other options like farm and sandboxed solutions, different types of apps, the benefits of apps, and their impact. It also mentions there will be a demo of apps in action. The document dives deeper into topics like the isolated sub-site each app receives, the app marketplace, and how apps are hosted either in SharePoint or externally.
More Related Content
What's hot
What's hot (18)
Viewers also liked
Similar to SharePoint 2013 Apps
Similar to SharePoint 2013 Apps (20)
Recently uploaded
Recently uploaded (20)
SharePoint 2013 Apps
- 1. Salman Ghani (MCPD SharePoint 2010, MCTS MOSS) 1st August 2012 SHAREPOINT 2013 APPS
- 2. Agenda Introduction to SharePoint 2013 Apps Compare with other options Apps Deep Dive Different Types of Apps What is good about Apps Impact of Apps Apps in Action (Demo) © 2012 www.salmanghani.co.uk. All rights reserved. 2
- 3. Introduction to SharePoint 2013 Apps A new method to deliver specific information or functionality Only Client side – no server side code directly in the app Isolated Stand-alone application New sub-site for each App Better solution for Cloud Discover and download Apps Installed, upgraded or uninstalled Public Apps Store by Microsoft © 2012 www.salmanghani.co.uk. All rights reserved. 3
- 4. Compare with other options Farm solutions Full access to the API Server side code On prem deployment only Sandboxed solutions Limited access to the sub set Server side code Online deployment Apps Isolated applications No server side code access Download marketplace © 2012 www.salmanghani.co.uk. All rights reserved. 4
- 5. Compare with other options What is possible in Apps Custom Web Parts Event receivers and Feature receivers Custom field (column) types Custom web services built on the SharePoint Service Application Framework Application Pages What is not possible in Apps Custom site definitions Delegate controls Custom themes Custom action groups and custom action hiding User controls (.ascx files) © 2012 www.salmanghani.co.uk. All rights reserved. 5
- 6. Apps Deep Dive Separate Sub-site for each web app Apps Experience Immersive App Experience Part App Custom Action App Scopes Web Scoped Tenant Scoped App Marketplace Public store Corporate Private store © 2012 www.salmanghani.co.uk. All rights reserved. 6
- 7. Apps Deep Dive (Apps URL) Deployed to their own web site Isolated domain name Layer of Isolation Processes don’t affect the SharePoint sites Prevent cross site scripting between the apps and sites Prevent unauthorised access to the user data Each App has unique URL Can choose template for URL © 2012 www.salmanghani.co.uk. All rights reserved. 7
- 8. Types of Apps SharePoint-Hosted Everything stays in isolated AppWeb. Client side code Self / Developer Hosted Business logic resides external to SharePoint Using any technology (.Net, Java, PHP etc) Azure Auto-Hosted Limited to Cloud 365 © 2012 www.salmanghani.co.uk. All rights reserved. 8
- 9. Apps Hosting Options © 2012 www.salmanghani.co.uk. All rights reserved. 9
- 10. What is good about the Apps? Add quick functionality Safe for Farm Site owners to Add/Remove Apps Download from Public or Corporate Apps Store Suitable for Cloud Make migration easy © 2012 www.salmanghani.co.uk. All rights reserved. 10
- 11. Impact of Apps Must run Subscription Service and App Management Service Applications to use apps Must create the DNS domain to contain the URLs for apps Plan for capacity as each app creates a subweb © 2012 www.salmanghani.co.uk. All rights reserved. 11
- 12. Resources Overview of apps for SharePoint for SharePoint 2013 http://technet.microsoft.com/en- us/library/fp161230(v=office.15).aspx Plan for apps for SharePoint for SharePoint 2013 http://technet.microsoft.com/en- us/library/fp161237(v=office.15).aspx Build apps for SharePoint http://msdn.microsoft.com/en- us/library/office/apps/jj163230(v=office.15) Deploying and installing apps for SharePoint http://msdn.microsoft.com/en- us/library/fp179933(v=office.15).aspx © 2012 www.salmanghani.co.uk. All rights reserved. 12
- 13. THANK YOU
Editor's Notes
- 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.An app for SharePoint can contain functionally equivalent remote event receivers.An app can deploy a new field (column) that is based on one of the existing field types. Another option is to present your data in a remote web page with customized controls or grids.You can develop your custom web services as remote services.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.
- App experiences - three different options on how your app is presented to consumers. There are three options, one exists for all apps and your app may use one or all three of them. Every app has what is called an (1) Immersive App Experience. This is when the app takes over the entire page similar to how the Office Web Apps work. Every app has this experience because every app has a start page. This may be as simple as a "About This App" or a help page. The other type is a (2) Part App. This is when the app is surfaced on part of a page, similar to how a Web Part works. Think about a weather app… it just provides a widget to show the weather from some location on a page. The last type is an (3) Custom Action App. In this scenario your app may just expose itself as a Ribbon control or menu item. A good example of this would be to submit a document to a printing service. The printing service may have an app in the Marketplace and when it is installed in a site, you get a new option on Word or PDF documents to submit to the printing company.Scoping apps - two choices for how your apps are scoped. When building a new app you have to decide what the scope of the app will be. Will it be (1) Web Scoped in that your app's resources will live only within the AppWeb or will it be (2) Tenant Scoped in that the app will connect to a bigger service that is architected in a multi-tenant way. Don't go looking for some checkbox in Visual Studio 2012, this is more of a "how did you build it" type thing.Obtain apps through the Public or Corporate Marketplace. Just like the phone, apps are published to the Marketplace where people can acquire them or even buy them. There is a Public Marketplace for Office 365… this works a lot like the phone Marketplace. The Corporate Marketplace is where a tenant [company] can have their own private Marketplace for their employees. Each Web App can get it's own Corporate Marketplace.
- SharePoint-Hosted App: In this scenario everything stays "with SharePoint." What I mean is that your app gets it's own isolated AppWeb when installed and can create & leverage things in SharePoint like site columns, content types, lists, libraries and pages. Any business logic must run in the context of the client (browser) so we're talking JavaScript.Self-Hosted / Developer-Hosted App: It will be curious to see what Microsoft tries to call this as it went by both names for a while in the betas. Basically in this scenario the bulk of the app, or the business logic, resized external to SharePoint. This could be using any technology (.NET Framework, Java, PHP, LAMP, etc) on any infrastructure (IIS, Apache, Windows Azure, Google Compete, Amazon EC2, etc). There is a SharePoint-hosted app that might not do anything but just be a launching pad to the external app, or it might have a good mix of both. The "self" or "developer" part of the name comes from the fact that the developer (or customer) is responsible for standing up the external piece & wiring the app & external piece together.Azure Auto-Hosted App: This one is quite interesting but is only available in the cloud (Office 365) at the time of RTM. Basically if your app needs to have an external component, you can build this type of app and deploy it to the Marketplace. When a user purchases/acquires your app and installs it, SharePoint not only creates the AppWeb to host the SharePoint piece of the app, but it automatically provisions a new Azure Web Site & optional SQL Azure database and automatically wires the SharePoint & Azure components together. The app would be installed in a special Azure subscription tied to your Office 365 account. Because these types of apps run in Azure, you're only limitation are the different offerings Azure provides for platforms. These include .NET Framework, Java, PHP & Node.js.