Some General Difference Between Microsoft Office SharePoint and SharePoint Server 2010

MOSS 2007 Vs SPS 2010

I have noted down some difference between MOSS 2007 Vs SPS 2010. I have also refered some points form MSDN and other MVP's blogs. Hope you will like these.

Microsoft Office SharePoint Server 2007	SharePoint Server 2010
Office client required to view and edit documents uploaded to document libraries (Download and open)	Office Web Application enables Word, PowerPoint, Excel and Visio documents, using Silverlight or HTML with JavaScript (Depending on Browser Support)
No Co-Authoring Capability	Co-Authoring Capabilities available for Word, PowerPoint (with client software) and Excel (Available over the web)
Lot of post backs	Fewer post backs for default actions – more Ajax usage
No inherent support of Ajax or Silverlight	Fully supported
Static themes. You just pick a theme and its applied across the site, no preview	You can select a theme , customize it and preview before applying it on the site
No bookmarking, tagging or rating capability	Its all there
Content Types scoped to site collections	New concept of having a Content Type hub which can be shared across web applications
Media files would have to be downloaded before playing	Progress download feature available (not streaming)
BDC used to store info in SharePoint	BCS reads data real-time (with some caching for performance)
5 million item limit in document library	10 million
Views are CAML driven	Views XSLT based
To query a list we had to use CAML	Queries via LINQ, JavaScript and Silverlight API’s
No restriction for installation	Ability to prevent people from installing SharePoint (Managed at the AD level)
Shared Services scoped to Farm	Shared Services architecture changed to make it more flexible and ability to share across farm
Profile synch could be done by anyone	Additional permission check for account to carry out profile synch
Basic web Analytics	Web analytics capability enhanced
Search results are static	Clicking on a search result affects the search results for the other searches for the same keyword
To limit issues with rogue code that could bring down the server, CAS had to be defined /maintained for different applications. This was not easy to do and Admins used to say – no code allowed	Sandbox available that restricts the scope of code. Deployment is also easy, the code just needs to be uploaded by the site admin, no need for intervention from the SharePoint farm admin to run scripts on the server
People with contribute access could upload .aspx pages in a document library. It was possible to restrict, however it would restrict everyone from uploading .aspx pages	People with contribute access cannot load .aspx pages
Contributors could edit tool pane parameters	Not editable by contributors
Explorer view on browser	Opens up Windows explorer with web dav access
Simplistic Mobile Page OOTB	Able to create richer mobile pages using OOTB features
Usage of outlook for offline access	SharePoint Workspace used for offline access – more capability eg. ability to synch up lists (even external content from BCS)
Not possible to have a common document ID that is associated with a document regardless of which document library it moves into	Document ID can be defined and associated to the document regardless of where it is located(within the site collection)
To upload a document or page, one needs to go to that appropriate site/subsite and library and upload	Content organizer moves document to appropriate libraries based on metadata rules which can be defined
When a file with a same name is uploaded, it creates a new version	Option to have another version or append a unique ID to the document being uploaded
Fixed layout with defined web part zones where web parts can be placed	More “Fluid” UI; ability to place web parts without having web part zones
Retention policy allows only delete or invoke workflow by default	Multiple other options – eg send to another library etc
EBS – to store docs out side SharePoint, possible but not easy to configure	RBS -  managed by SQL
Requires Server OS to install(32 or 64)	Can be installed on Win 7 (64 bit) and Win 2008 (64 bit)
No field validations	Field validations available
Workflows created in SPD or VS.Net – not possible to move a workflow developed in SPD to VS.Net	Workflows can be defined in Visio, Imported to SPD with rules added and then moved to VS.Net
Table based layouts	Div Based layouts (better for accessability)

SP 2010	MOSS 2007
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	In MOSS 2007 there is no ribbon
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	In MOSS 2007 you need to drag the dll either to bin or GAC
Silverlight Application
In SP 2010 we can create a Silverlight application directly from Visual Studio 2010	In MOSS 2007 we have to create a web part to host Silverlight application
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	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 between the forms
In SP 2010 we can update existing information	In MOSS 2007 through we can just read the information and we can't update the existing services
Improvement in Deployment
In SP 2010 we can Deploy through Farm based and solution based solution in SP 2010	In MOSS 2007 there is no such option
Alerts
In SP 2010 it has been improved in validation and unique values. While creating column itself we have an option "Allow Duplicate values" to Yes or No	In MOSS 2007 alerts were sent only through emails but in SP 2010 users can also 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
Improvements of events
New events for list creation and web creation	No List and web events in MOSS 207
Getting Items from the list
In SP 2010 through object model we can fetch multiple list data by LINQ query and object model	In MOSS 2007 we can fetch only through object model
Rating
In SP 2010 we can have rating column by default	In MOSS 2007 we should install the feature that is available in codeplex to have rating
Key Word Suggestions
In SP 2010 we can have keyword suggestions	In MOSS 2007 we don’t have any keyword suggestions
Taxonomy
In SP 2010 we can create Taxonomy by using Managed Metadata service	In MOSS 2007 we don’t have taxonomy
Other Features
In SP 2010 we have Power Shell Scripting, JavaScript object model, Chart Web Parts	In MOSS 2007 we don’t have Power Shell Scripting, JavaScript object model, Chart Web Parts
Running stsadm command
In SP 2010 we have to go 14 hive path to run stsadm command	In MOSS 2007 we have to go 12 hive path to run stsadm command