Sharepoint Difference FAQs-1 1.Difference between .NET and Sharepoint S.No 1 .

NET Functionality Creation: Sharepoint Functionality Creation:

Code need to be written even Lots of pre-defined web parts and to achieve simple functionality elements available.No need to write the code. 2 Coding Effort: Coding Effort:

Takes time to create the code Very less time required and test 3 Skilled Professionals: Skilled professionals required to create functionality 4 License Requirement: Skilled Professionals: are Even novice professionals can do the so easily License Requirement:

Not required at the time of Free versions available, but in case deployment of solution of extensive requirements License is required 2.Difference between Site Template and Site Definition S.No 1 Site Templates Site template approach for SharePoint Site Creation is easier, and just requires the use of the Web interface and occasionally Microsoft FrontPage. Content can be saved with site template Site Definitions Site Definitions are the foundations on which all sites and user templates are built. Site Definition is collection ox XML and .aspx file. Site Definitions are predefined components needs to be included when a site was created in SharePoint server. Site Definition contains information of Web Part , Lists, Features and navigation bars to be included in the site disk, better

2 3

Files are in content database, Files are on less efficient. performance.

Not easily extensible (users Highly customizable and extensible are limited by what UI offers) (XML and .NET code is much more flexible than UI) Can only provide one web Can provide multiple webs

3.Difference between SharePoint 2010 and MOSS 2007 S.No 1 SharePoint 2010 Look and feel: MOSS 2007 Look and feel:

In SP 2010 look and feel In MOSS 2007 there is no ribbon perspective there will be a ribbon where we can have a look and feel like Office 2010 2 Deployment of Web parts : Deployment of Web parts :

In SharePoint 2010 deploying In MOSS 2007 you need to drag custom web part is pretty the dll either to bin or GAC simple i.e. just right click on the solution and click Deploy 3 Silverlight Application: Silverlight Application:

In SP 2010 we can create a In MOSS 2007 we have to create a Silverlight application directly web part to host Silverlight from Visual Studio 2010 application 4 Shared Database & Service Shared Database Application: Application: In SP 2010 there is no SSP but there is a concept of Service Application like BCS as one service application, Excel Services as another service application, User Profile as separate service application. General idea is that you have an application for each service, rather than one application with lots of service crammed into it Own database rather than shared database in SP 2010 5 & Service

In MOSS 2007 we have SSP where we can work around with BI,Search Settings, User Profile Import, Excel Services, Info path In Database also we use to have separate area for SSP stuff

Easy exports/imports Easy exports/imports between between the forms : the forms : In SP 2010 we can update In MOSS 2007 through we can just existing information read the information and we can't update the existing services

Improvement Deployment :

in Improvement in Deployment :

In MOSS 2007 there is no such In SP 2010 we can Deploy option through Farm based and solution based solution in SP 2010 7 Alerts: Alerts:

In SP 2010 alerts were sent In MOSS 2007 alerts were sent only through emails and send only through emails. alerts to mobile device as SMS message. A New property delivery channel is introduced to indicate, whether the alerts is delivered as Email or an SMS message. 8 Improvements of events : Improvements of events :

New events for list creation No List and web events in MOSS and web creation 2007 9 Getting Items from the list : Getting Items from the list :

In SP 2010 through object In MOSS 2007 we can fetch only model we can fetch multiple list through object model data by LINQ query and object model 10 Rating : Rating :

In SP 2010 we can have rating In MOSS 2007 we should install column by default the feature that is available in codeplex to have rating 11 Key Word Suggestions : Key Word Suggestions :

In SP 2010 we can have In MOSS 2007 we dont have any keyword suggestions keyword suggestions 12 Taxonomy : Taxonomy :

In SP 2010 we can create In MOSS 2007 we dont have Taxonomy by using Managed taxonomy Metadata service 13 Other Features : Other Features :

In SP 2010 we have Power In MOSS 2007 we dont have Shell Scripting, JavaScript Power Shell Scripting, JavaScript object model, Chart Web Parts object model, Chart Web Parts

14

Running stsadm command :

Running stsadm command :

In SP 2010 we have to go 14 In MOSS 2007 we have to go 12 hive path to run stsadm hive path to run stsadm command command Reference: http://onlydifferencefaqs.blogspot.in/2012/08/sharepoint-difference-faqs-1.html SharePoint 2010 vs SharePoint 2013 Difference between SharePoint 2010 and SharePoint 2013 S.No 1 Sharepoint 2010 What is SharePoint 2010 -It is a previous or I should say current version of SharePoint that was released in year 2010. Sharepoint 2013 What is SharePoint 2013 (Preview) 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. Development Changes In SharePoint 2013 Microsoft Introduced a new Cloud App Model for designing Apps for SharePoint. Apps for SharePoint are selfcontained 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. Tools SharePoint 2013 has Introduced new Tools for App development. Visual Studio 2012 now lets you develop apps for SharePoint and apps for Office. In addition a new web-based tools called Napa Office 365 Development Tools

Development Changes 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. In SharePoint 2010 developers were also developing Farm solutions as they did with the previous SharePoint 2007 version.

were introduced for developing 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.

Social and Collaboration features -SharePoint 2010 had very few social capabilities. My sites Tags and Tag profile pages Notes

Social and Collaboration features 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

Search SharePoint 2010 had Introduced Integrated FAST search as an Enterprise search. In addition to this buildin SharePoint search is still widely used in companies.

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

Enterprise Content Management (ECM) -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

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

primary tool to modify Master pages instead of the new Design Manager.

EDiscovery

Reference: http://onlydifferencefaqs.blogspot.in/2012/09/difference-between-sharepoint2010-and.html Apps vs Farm Solutions Difference between Apps and Farm Solutions in SharePoint 2013 S.No 1 Apps What are apps An app for SharePoint is a small, easy-to-use, standalone app that solves a specific end-user or business need. Where does it run The code for an app runs in different places, depending on where your app is hosted.They never run in the context of SharePoint Server, but they will run in the context of the browser or in the context of the hosted platform. SharePoint-hosted apps Provider-hosted and autohosted apps In the cloud Apps that have a mix of components in SharePoint and in the cloud Farm Solutions What are Farm solutions - Farm solutions are pieces of functionality that extend the capabilities of a SharePoint website. They are Installed to the solution store of a farm by a farm administrator. Where does it run They are Installed to the solution store of a farm by a farm administrator. They run from the sharepoint server.

How Does It run - When you deploy a SharePoint-hosted app, SharePoint creates a new website called the app web. You can think of it as a dynamically created safe

How Does It run when you deploy a Farm solution, It gets deployed to one or more web apps (any existing or new one). You can use it in any site collection of the web app where

space for your app. Besides you deployed it. allowing you to store pages, lists, and libraries, the app web is also an isolated endpoint that your app can securely call client side by using JavaScript. 4 Authentication options - Authentication options - The Before you can call SharePoint components in the solution can, APIs from your app, you need and usually do, run in full trust to authenticate to SharePoint. Which authentication mechanism you use depends upon where the code of your app is running. * Inside SharePoint: You have to use HTML and JavaScript, and authentication is already taken care for you. * In the cloud: You have two choices: Use client-side code along with the cross-domain library. User server-side code along with OAuth. *REST APIs Resource Allocation - Resource Allocation No Site collection administrators resource usage restrictions are and tenant administrators can placed on them monitor apps and change the resources allocated to them. What Can be Created as What Can be Created as Farm soltuion - You can deploy almost Custom Web Parts all the components as Farm (remote pages that solution. contain custom Web Parts) Event receivers and Feature receivers(remote event receivers) Custom field (column) types () Custom web services built on the SharePoint Service Application Framework Application pages Cannot be created as

Apps Apps cannot call SharePoint server side code Apps cannot access SharePoint components that are not on the same site Apps cannot communicate with each other Custom site definitions Custom themes Custom action groups and custom action hiding User controls (.ascx files) Delegate controls

Reference: http://onlydifferencefaqs.blogspot.in/2012/09/difference-between-apps-andfarm.html Difference between Asynchronous Event Handler and Synchronous Event Handler in Sharepoint Difference between Asynchronous Event Handler and Synchronous Event Handler in Sharepoint S.No 1 Asynchronous Event Handler(AEH) When it fires: AEH will fire after the event is completed. Event Cancellation: It is not possible to cancel the event from AEH. Synchronous Event Handler(SEH) When it fires: SEH will work before the event is completed Event Cancellation: SEH are mostly used to stop the event from completion in order to validate few things. It means we can cancel the event using SEH Method Names Identification: SEH methods has their method names ending with -ing. e.g. ItemAdding, ItemUpdating are SEH methods

Method Names Identification: AEH method names will end with -ed. e.g.ItemAdded, ItemUpdated are AEH methods.

To add/modify list fields To add/modify list fields values: values: Possible Not Possible as it fires after the completion of event.

Reference: http://onlydifferencefaqs.blogspot.in/2012/08/difference-betweenasynchronous-event.html onPremise vs Online Difference between SharePoint onPremise and SharePoint Online in Sharepoint 2010 Features Sharepoint OnPremise Composites Developer Dashboard SharePoint Timer Jobs Business Data Integration with the Office Client Business Connectivity Services Profile Page Yes Yes Yes Sharepoint Online Composites No No No

Yes

No

Content Records Center Audit Opening and Downloading Word Automation Services Yes Yes

Content No No

Yes SharePoint Insights

No SharePoint Insights No

Business Intelligence Center

Yes

Chart Web Parts Data Connection Library PerformancePoint Services Dashboards Decomposition Tree Excel Services and PowerPivot for SharePoint

Yes Yes Yes

No No No

Yes Yes Yes

No No No

SharePoint Search Advanced Content Processing Tunable Relevance with Multiple Rank Profiles Business Intelligence Indexing Connector Yes

SharePoint Search No

Yes

No

Yes

No

SharePoint 2010 Yes Search Connector Framework Contextual Search Deep Refinement Federated Search Query Suggestions, "Did You Mean? and Related Queries Relevancy Tuning Yes Yes Yes Yes

No

No No No No

Yes

No

Rich Web Indexing Enterprise Scale Search Windows 7 Search Similar Results Thumbnails and Previews Visual Best Bets

Yes Yes Yes Yes Yes Yes

No No No No No No

SharePoint Sites SharePoint Sites Web Analytics Public Website Office Web Apps integration Secure Store Service Yes Yes Yes Yes No Yes (One per site owner) Yes (Preconfigured) Yes (Per owner) site

Reference: http://onlydifferencefaqs.blogspot.in/2012/09/difference-between-sharepointonpremise_11.html Sandboxed vs Farm Solutions Difference between Sandboxed and Farm Solutions in Sharepoint 2010 S.No 1 Farm Solution Sandboxed Solution

Where assemblies are kept ? Where assemblies are kept ? Any assemblies associated with a Assemblies are placed in the solution are extracted, kept in GAC or in the Bin directory of a memory, and executed within a SharePoint web application. special worker process called Assemblies placed in the GAC SPUCWorkerProcess.exe. This are fully trusted,whereas isolates assemblies placed in the bin the execution of sandboxed directoryof a web application solutions from the Operations of can be partially trusted. the underlying web process. Assembly execution takes place in the web Server

process (w3wp.exe). 2 Who has authority to install and deploy solutions ? Solutions must be installed and deployed by a farm administrator. Is there any limitation on Sharepoint classes and objects when developing Farm Solution ? There are no limitations on which SharePoint classes and objects can be used in farm solution Assemblies. Throttling of server resources can be done or not ? Solutions will use however many server resources are necessary. Who has authority to install and deploy solutions ? Solutions can be installed and deployed by a site administrator . Is there any limitation on Sharepoint classes and objects when developing Farm Solution ? Developers must leverage a subset of the SharePoint API when developing sandboxed Solutions. Throttling of server resources can be done or not ? Farm administrators have the ability to throttle the server resources used by a given solution.

Reference: http://onlydifferencefaqs.blogspot.in/2012/09/difference-between-sandboxedand-farm.html