CSOM vs JSOM vs SSOM vs REST

Sharepoint 2013

Model Types:

• CSOM Client-side object model. C# (or Visual Basic) only
• JSOM JavaScript object model. JavaScript only.
  • SP.ClientContext.get_current() for normal use. new SP.ClientContext('url...') for specific SPSite. Note this works cross-SPSite in 2013.
• SSOM Server-side object model.
• REST REST web technologies and standard Open Data Protocol (OData) syntax.
  • Either JS (JavaScript) or C# (or Visual Basic)

Technologies table:

	CSOM	JSOM	SSOM	REST JS	REST C#
JavaScript
C#
From browser
From server
OAuth2
S2S

Hosting table:

	CSOM	JSOM	SSOM	REST JS	REST C#
SharePoint hosted
Autohosted
Provider hosted
Sandboxed solution			(Limited)
Farm solution

Fix for SharePoint 2010 scrolling problems

Scrolling did not work when visiting the site. I was able to identify that the source of these scrolling issues was due to the manner in which the static placement of the SharePoint style was implemented.

The Solution

The solution is simple just add following style to page

    body.v4master { overflow:auto; }

ASANA type task management in sharepoint using Angularjs

Hi, i have created new app in sharepoint. ASANA type Task Management System

Download

CRUD in sharepoint 2013 using angularjs

Hi, today i have created new app in sharepoint. This is my first app in sharepoint

Download

Differences between hosting options for SharePoint apps

When we create a new app in Visual Studio, we are given the option to select an hosting model:

So, a quick introduction of the different hosting options. It is really based on your requirements which one you should / need to choose.

SharePoint-hosted App

Start with the simplest option: SharePoint-hosted apps, or apps where all components are hosted on either an on-premises or Office 365 SharePoint farm. SharePoint-hosted apps are installed on a SharePoint 2013 website, called the host web. They have their resources hosted on an isolated subsite of a host web, called the app web. It’s important to know the difference between host webs and app webs.

Get these benefits	But consider this
Reuse common SharePoint items, like lists and Web Parts.	You can use only JavaScript in the add-in—you can’t use any server-side code.
Relatively easy to create and deploy, so they are good for small team productivity add-ins and business process automation, with lower complexity business rules.	Your add-in has only the authorization privileges of the signed-in user.

Provider-hosted App

Provider-hosted apps for SharePoint include components that are deployed and hosted outside the SharePoint farm. They are installed to the host web, but their remote components are hosted on another server.

Get these benefits	But consider this
Host the add-in on Microsoft Azure or any remote web platform, including non-Microsoft platforms.	You are responsible for creating the installation, upgrade, and uninstallation logic of the remote components.
Use one of the SharePoint client object models, the JavaScript cross-domain library, or the SharePoint 2013 REST/OData-based web service to interact with SharePoint.	Each way of interacting with SharePoint has corresponding options for approaches to data access.
Gain authorization to SharePoint data using one of the three authorization systems.	You need to decide between OAuth and the cross-domain library to authorize your add-in’s access to SharePoint.

Deciding on a hosting pattern. You can use the following table to help sort out which hosting pattern best fits your needs.

Your requirements	Recommended Hosting pattern	Example
Work with and provision new SharePoint entities exclusively	SharePoint-hosted	An add-in that includes a people picker control and that stores information about SharePoint users in a SharePoint list
Use existing SharePoint entities and interact with external (non-SharePoint) web services	Provider-hosted	An add-in that gets customer addresses from an existing SharePoint list in the host web and uses a mapping service in a web application to display their locations
Provision new SharePoint entities and interact with external web services	Combined SharePoint-hosted and provider-hosted	A mapping add-in that provisions a SharePoint list on the appweb so that it can store latitude and longitude coordinates for addresses that are supplied by the user or pulled from an existing SharePoint list

App Management Shared Service Proxy is Not Installed -- Error --

In this article you will see how to resolve the issue "Error: App Management Shared Service Proxy is not installed" in SharePoint 2013.

Reason

This is because the App Management Service application is not created or the App Management Service is not running or the App Management Service Proxy is not added to the default proxy group.

Solution 1

1. Open "Central Administration".
2. Click on "Application Management" in the quick launch bar.
3. Click on "Manage Service Applications" available under the Service Applications section.
   
4. Check whether the App Management Service application is created, if not then create the App Management Service application.
   
   
   
   
5. Click on "Application Management" in the quick launch bar.
6. Click on "Configure service application associations" available under the Service Applications section.
7. Check whether the App Management Service proxy is added to the default proxy group, if not then add it to the default proxy group.
8. Click on "Application Management" in the quick launch bar.
9. Click on "Manage services on server" available under the Service Applications section.
   
10. Check whether the App Management Service is started, if not then start the service.

Solution 2 : Powershell

1. Launch SharePoint 2013 "Management Shell"
   
2. Get the Farm account
   $account = Get-SPManagedAccount FarmAccount
3. Create a new application pool using this account
   $appPoolAppSvc = New-SPServiceApplicationPool -Name AppServiceAppPool -Account $account
4. Create the "App management" service application, using this application pool
   $appAppSvc = New-SPAppManagementServiceApplication -ApplicationPool $appPoolAppSvc -Name AppServiceApp -DatabaseName NomDeLaBDD
5. Create a proxy for the service application
   $proxyAppSvc = New-SPAppManagementServiceApplicationProxy -ServiceApplication $appAppSvc
   
6. Start the "App Management Service" service
   Get-SPServiceInstance | where-object {$_.TypeName -eq "App Management Service"}
   (Get-SPServiceInstance | where-object {$_.TypeName -eq "App Management Service"}).Provision()
   Get-SPServiceInstance | where-object {$_.TypeName -eq "App Management Service"}
   

App Part vs Web Part

	App Part	Web Part
Environment	An App webpart can run outside the SharePoint environment	Web Part has to run under the SharePoint premises.
Deploy	An App webpart can be deployed to the Cloud premises	Web part has to be deployed in the OnPremises server.
Crashes	If an App web part crashes, it won't significantly impact the SharePoint farm	Whereas, in case of the webpart, it does affect the farm.

Sharepoint 2013 Vs Sharepoint 2010

	SharePoint 2013	SharePoint 2010
What is it	A new version of Microsoft famous Collaboration portal called SharePoint. The version adds few new exciting features such as Social Feed,SharePoint Apps and cross-site publishing.	It is a previous of SharePoint that was released in year 2010.
Development Changes	In SharePoint 2013 Microsoft Introduced a new Cloud App Model for designing Apps for SharePoint. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. You can use HTML, CSS, JavaScript and protocols like the Open Data protocol (OData), and OAuth to communicate with SharePoint using Apps No more Sandbox solutions. SharePoint 2013 sandboxed solutions are deprecated. So all we got is the New App model and the Old SharePoint Farm solutions. check out	SharePoint 2010 Introduced Sandbox solutions to help developers deploy code that did not effect the whole farm. In SharePoint 2010 you could use Server Object model and Client Object model (.Net Managed, ECMASCRIPT and silverlight) to extract data from SharePoint.
Social and Collaboration	Microsoft in SharePoint 2013 Introduced new Social capabilities for better collaboration in the company.New Features added are Interactive feed Community Site Follow people Follow Sites	SharePoint 2010 had very few social capabilities. My sites Tags and Tag profile pages Notes
Search	SharePoint 2013 includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Some of the features added are Consolidated Search Results Rich Results Framework keyword query language (KQL) enhancements	SharePoint 2010 had Introduced Integrated FAST search as an Enterprise search. In addition to this build-in SharePoint search is still widely used in companies.
Enterprise Content Management (ECM)	SharePoint 2013 added some of the best capabilities of an ECM software. The newly added stuff is Design Manager Managed Navigation Cross-site Publishing EDiscovery	SharePoint 2010 on the other hand had Introduced Managed metadata and taxonomy as a part of new ECM benefits for SP 2010. This version did not had Managed Navigation and Cross-site Publishing. SharePoint designer was a primary tool to modify Master pages instead of the new Design Manager.