App Catlog :
In this multi part series, I’ll try to cover all the details related to SharePoint Add-ins (SharePoint App). In this article I’ll start with the introduction/basics of SharePoint Add-ins.
First of all, Microsoft has changed the name “app for SharePoint” to “SharePoint Add-ins”. Reference - New name for apps for SharePoint
First important point in this series to understand is Tenancy.
Tenancy : A SharePoint Tenancy is a set of site collections. These set of site collections are administrated as a unit.
1. SharePoint Tenancy in Office 365: When any organization / company purchase licenses of Office 365 for SharePoint sites (SharePoint online) Office 365 creates the new tenancy. The users who access the tenancy are called as Tenants.
When new tenancy is created in Office 365, for SharePoint an administrative site collection is created. This site collection is accessible to the SharePoint online administrators (also called Tenant administrator).
This SharePoint admin site is similar to Central Admin application in SharePoint on premises as
|Office 365 - SharePoint admin center|
In left side there is settings for SharePoint features like InfoPath, bcs, apps etc.
2. SharePoint Tenancy in On Premises: Concept of Tenancy is introduced in SharePoint 2010. In On premises, farm level default tenancy is created in background. This farm wide tenancy enables the installations of SharePoint apps in on-premises farm since apps are always installed and run within the context of tenancy
Basics of SharePoint Add-ins:
- SharePoint Add-ins are stand-alone components implemented to solve specific requirement and can be added on multiple sites.
- SharePoint Add-in code never runs in SharePoint. All custom code is either executed in client machine or in cloud or in another server depending upon which type of SharePoint Add-ins we are implementing.
- SharePoint Add-in code is authenticated and runs under separate identity. I’ll explain in more details in upcoming articles
- We developers need to take decision depending on the scenario / requirement which type of Add-ins we need to develop
- In SharePoint 2013 everything is Add-ins/App means features in SharePoint like List, Libraries etc.
- Following are the few examples of SharePoint Add-ins
- Site Creation Wizard - Approval mechanism : Employees of the company/organization can request the creation of sites/workspaces and request will be sent to specific group of peoples to approve.
- Feedback App : Where end users of site can give the feedback to site administrators
- Apps are stored in specific site called App Catalog. Once App catalog site is created, we can use it to upload the apps which we developed so that those apps will be available for the users to install those apps
- In On premises environment, App-catalog site is specific to web application. There is only one App catalog site per web application
- In Office 365 / SharePoint online, App catalog site is created at tenancy level.
Types of SharePoint Add-ins :
1. SharePoint hosted
2. Provider hosted
I’ll conclude here, in next upcoming articles we will see more details, starting with the development of each type Add-ins, various development approaches for each type of Add-ins, authentication and authorization for Add-ins and so on.
Enjoy Reading :)
As usual any feedback / query / suggestions are most welcome !!!