Skip to main content

SharePoint Apps Introduction | which you should know before develop with SharePoint App model

With the rise of cloud platform and cloud model (office 365), app model came into conversation with addressing the some of the drawbacks which was with SharePoint custom solutions. Even though there are many disadvantages with the App model solution designers go to this model with the requirement.

Following few points better to know before jump into the model;

  • W3wp.exe – SharePoint worker process which manages solutions which deployed as a farm solution

  • SPUWorkerProcess.exe – worker process which manages solutions which deployed as a sandbox solution

Since all the models which were before running inside the SharePoint, there is high couple and dependencies which can be accounted as a disadvantages.

  • There is possibility of custom codes affect the processes and codes of SharePoint – scalability and environment risks

  • Less ability to upgrade the SharePoint with the tightly coupled behavior and its complex behavior – high dependencies

  • When code running with elevated privilege can do any action which site administrator (security violation with impersonation) can do. Sandbox box solutions scope this impact to some extent but code within the scope will affected – permission issue

  • Sandbox solutions it’s not possible to run code with impersonation and only capable of running codes as current user – impersonation issue

  • Final major problem with the installation and upgrading. This may require restart of IIS on front-end servers – installation and upgrading issue

Impersonation in SharePoint

Running custom codes as an administrator to perform some task which signed in or other users could not perform. This achieved by using SPSecurity.RunWithElevatedPriviledges.

Advantages of SharePoint app model

  • App support for both Office 365 (cloud) and on premise

  • App code runs separately apart from SharePoint environment

  • Code can be run under distinct authentications

  • Apps deployed using app catalog make easier to discover, install and upgrade

  • App code access the SharePoint point across web service entry points

SharePoint tenancy

Set of site collections configured and administered as a set (bundle). Business users who access the tenancy knows a tenants.

When O365 creates new tenancy, it created new administrative site collection with can be accessibly by the tenant administrator.

When deploying apps into SharePoint on premise it takes “default tenancy” where tenancy concept that much not important.

Services which supports for SharePoint app model

App Management Service

It contains configuration data for Apps which installed, configured, permissions and licensing of SharePoint apps. This can be configured manually in the ‘Central Administration’ and it’s already configured in the Office 365.

Site Subscription Setting service

Contains configuration data of every site tenancy and includes those in its own database. This need to be configured using PowerShell and pre-configured in the Office 365.

Scopes of SharePoint Apps (App installation scopes)

1. Site Scope

Launched and installed in the same scope of SharePoint site.

2. Tenancy Scope

App installed in special type of SharePoint site known as “app catalog”. So that users can use the app in site as they prefer. This scope is useful when users in the tenancy can pick the app and use in their site as prefer. Permission handling on app still with the administrator.

There are two isolated places where you can push custom codes to SharePoint. Those are as bellows;

  • Client side – runs on the client’s browser. You could write with JavaScript, Silverlight, VBScript, Flash or whatever client side scripting technique. This always act as a “SharePoint hosted app”

  • Server side – can be write with language like C# and this need to execute code outside the SharePoint host environment. This mostly become a cloud hosted app.

In later post I will be further talking about hosting models, configuration files within the apps, packaging and etc.




Popular posts from this blog

Turn off/ Hide Details panel/ Information Panel on modern SharePoint lists

Not always we require to show changes done by other which is a mandatory feature in SharePoint online.  What is details pane (aka. Information Pane)? Detail pane/ Information shows information regarding the document if you selected a one or its showing recent changes within a list or library. Follow link to Microsoft documentation about details pane. Bad news: Until Microsoft listen to User Voice , there is no straightforward way to enable disable this even you don't want. Good news: We could write a SharePoint framework extension to hack styles until Microsoft give us a permanent solution. How? I found this sample project (Inject CSS into modern SharePoint pages with React) which could reuse to our purpose. Thanks to Hugo for saving my time.  Steps to awesomeness:  Clone the project Resolve dependencies >  npm i Bundle >  gulp bundle --ship Package >  gulp package-solution --ship Upload package into SharePoint App catalog  

File attach (POST) to SharePoint 2013 List (custom) using Angular JS via REST API

Following describes how to upload attachment to SharePoint 2013 custom list using Angular JS. Note: You can be consumed the JSOM libraries to achieve this, but there is limitation of 1.5 Mb. Better approach would be consuming exposed REST API (SharePoint OOTB) which allowed up to 2 Gb of file to attached using client side scripts i.e. Angular JS. . Here I have used the “Angular File Upload” which capable of doing more tasks other than basic HTML input file control. By consuming this we can attach multiple files either to the list and etc. You can be found the information on how to include this module to your Angular view in following link. Use package manager command to install the scripts. For bower  -->        bower install angular-file-upload For nugget -->       npm install angular-file-upload It requires file buffer array to POST (save) our attachment via REST API, browsers FileReader API is required to use. Its available with almost all common browsers. You need to ensure t

📢 Update -Microsoft Teams IP Phones and Intune Enrollment

For customers who require desk phones and conference room phones to make and receive audio calls or join meetings, Microsoft Teams provides a growing portfolio of devices that can be purchased from our Teams Marketplace . For Teams phones including the Yealink T56A/T58A/CP960 and the Crestron Flex series IP phones that run on Android 5.x or later, there may be specific configurations that need to be enabled in the customer's tenant for the phones to successfully enroll into Intune.      Allowing successful Intune enrollment for Android versions 5.x and up     If all the following conditions below are true , you will need to enable a specific configuration setting in the Intune admin console to allow for a successful enrollment:   You are deploying a Teams IP phone with Android OS version 5.x or later.   You have connected your Intune tenant with managed Google Play in order to manage Android Enterprise devices.   You have configured your enrollment restrictions such that A