Sharepoint Difference FAQs-1

1.Difference between .NET and Sharepoint

S.No	.NET	Sharepoint
1	Functionality Creation: Code need to be written even to achieve simple functionality	Functionality Creation: Lots of pre-defined web parts and elements available.No need to write the code.
2	Coding Effort: Takes time to create the code and test	Coding Effort: Very less time required
3	Skilled Professionals: Skilled professionals are required to create the functionality	Skilled Professionals: Even novice professionals can do so easily
4	License Requirement: Not required at the time of deployment of solution	License Requirement: Free versions available, but in case of extensive requirements License is required

2.Difference between Site Template and Site Definition

S.No	Site Templates	Site Definitions
1	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 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
2	Files are in content database, less efficient.	Files are on disk, better performance.
3	Not easily extensible (users are limited by what UI offers)	Highly customizable and extensible (XML and .NET code is much more flexible than UI)
4	Can only provide one web	Can provide multiple webs

3.Difference between SharePoint 2010 and MOSS 2007

S.No	SharePoint 2010	MOSS 2007
1	Look and feel: In SP 2010 look and feel perspective there will be a ribbon where we can have a look and feel like Office 2010	Look and feel: In MOSS 2007 there is no ribbon
2	Deployment of Web parts : In SharePoint 2010 deploying custom web part is pretty simple i.e. just right click on the solution and click Deploy	Deployment of Web parts : In MOSS 2007 you need to drag the dll either to bin or GAC
3	Silverlight Application: In SP 2010 we can create a Silverlight application directly from Visual Studio 2010	Silverlight Application: In MOSS 2007 we have to create a web part to host Silverlight application
4	Shared Database & Service 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	Shared Database & Service Application: 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
5	Easy exports/imports between the forms : In SP 2010 we can update existing information	Easy exports/imports between the forms : In MOSS 2007 through we can just read the information and we can't update the existing services
6	Improvement in Deployment : In SP 2010 we can Deploy through Farm based and solution based solution in SP 2010	Improvement in Deployment : In MOSS 2007 there is no such option
7	Alerts: In SP 2010 alerts were sent only through emails and send 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.	Alerts: In MOSS 2007 alerts were sent only through emails.
8	Improvements of events : New events for list creation and web creation	Improvements of events : No List and web events in MOSS 2007
9	Getting Items from the list : In SP 2010 through object model we can fetch multiple list data by LINQ query and object model	Getting Items from the list : In MOSS 2007 we can fetch only through object model
10	Rating : In SP 2010 we can have rating column by default	Rating : In MOSS 2007 we should install the feature that is available in codeplex to have rating
11	Key Word Suggestions : In SP 2010 we can have keyword suggestions	Key Word Suggestions : In MOSS 2007 we don’t have any keyword suggestions
12	Taxonomy : In SP 2010 we can create Taxonomy by using Managed Metadata service	Taxonomy : In MOSS 2007 we don’t have taxonomy
13	Other Features : In SP 2010 we have Power Shell Scripting, JavaScript object model, Chart Web Parts	Other Features : In MOSS 2007 we don’t have Power Shell Scripting, JavaScript object model, Chart Web Parts
14	Running stsadm command : In SP 2010 we have to go 14 hive path to run stsadm command	Running stsadm command : In MOSS 2007 we have to go 12 hive path to run stsadm command