SharePoint 2013: Frequently Asked Comparison Interview Questions

SharePoint 2013

SharePoint 2010

Branding - Design Manager is a new feature introduced in a publishing site which minimize the amount of SharePoint knowledge that is required to successfully design and brand a SharePoint site.

Significant SharePoint knowledge required to design the user interface for SharePoint sites.

Device channels - You can render a single published SharePoint site in multiple designs to accommodate different device types.

Teams can create mobile views for sites but not necessarily for different types of mobile devices.

Business intelligence -SharePoint Server 2013 enables a user to view certain kinds of dashboard content. This includes PerformancePoint reports and scorecards, and Excel Services reports in iOS 5.0 Safari browsers on iPad devices.

No such facility available here.

Follow people to see updates based on their Newsfeed posts and what they are publishing.

Users define core areas of expertise in the “Ask me about” column.

Activity posts are saved for as long as you decide to retain them (most organizations align this policy with email retention) and are searchable.

Users can post a single status that is not retained and not searchable.

Workflow – Significant enhancements, including new ways to create and visualize workflows.

Several “built in” workflows with additional options available in SharePoint Designer.

App web

Host Web

Sharepoint 2013 apps host its component into isolated domain called App Web.

Host web is not an isolated domain.

Site on which the App is deployed.

Site on which the App is installed.

Blocking cross site scripting attacks.

No direct provision for blocking cross site scripting attacks.

App web is default. CSOM ClientContext refers to the app web context environment by default.

In order to refer Host Web via ClientContext, we need to add proxy or cross domain call using CSOM.

Seattle Master

Oslo Master

It is Advanced form of master page.

Oslo is basic version of Master page. Oslo has a wider layout for your content.

Seattle is design for intranet site with more feature like social, site navigation etc.

Oslo design for published site which focus on page layout and content rendering.

Seattle layout is having Left navigation enable for site.

Oslo layout left navigation is disabled.

Seattle references corev15.css file.

<SharePoint:CssRegistration Name="Themable/corev15.css" runat="server" />

Oslo master references oslo.css file with EnableCssTheming set to true.

<SharePoint:CssRegistration Name="Themable/oslo.css" runat="server" EnableCssTheming="true" />

No security trimming control available here.

Oslo has SPSecurityTrimmedControl which is configured to hide the contents from the search crawler.

Top ribbon kept as it is.

<SharePoint:AuthenticatedUserDiv /> tag not present here.

The Oslo handles anonymous users differently. The top ribbon is completely removed for anonymous users.

<SharePoint:AuthenticatedUserDiv /> tag play important role in hiding content on page.

Visual WebPart

WebPart

Visual WebPart is combination of user control (.ascx) and assembly (dll).

WebPart is not having user control file included into it. We need to refer existing user control file inside WebPart to render UI.

Visual WebPart support localization. Mapping to resource folder under 14hive. Add new resource file and reference it in project.

No localization support.

Code separation makes it easy to maintain the functionality.

No code separation.

It gives greater productivity if we develop complex UI using user controls.

It provides flexibility.

ExecuteQueryAsync

ExecuteQuery() is part of server side object model.

ExecuteQueryAsync() is part of ECMAScript object model.

ExecuteQuery() is synchronous call. User code waits until SharePoint sends a response back.

ExecuteQueryAsync() is asynchronous call .

Syntax : ExecuteQuery();

Syntax: ExecuteQueryAsync(successCallback, failCallback) : method takes two callback parameters, which specify methods to execute if it succeed or fail.