SharePoint 2010 vs 2007


I am sure that Microsoft will be publishing a more detailed list like it had for 2007 vs WSS 3.0 vs 2003 but till then here is my version.
I tried to focus more on the differences, rather that new features, so I did not put anything on Access services etc., however that did not stop a lot of new things from coming up.

I felt that doing this would enable a person who understood SharePoint 2007 get a grasp of 2010 in one shot, rather that go through the maze of documentation thats available.

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)
Advertisements

13 comments

  1. […] https://jacksonc.wordpress.com/sharepoint-2010-vs-2007 moss , Sharepoint 2010 Sharepoint / MOSS / WSS, Sharepoint 2010 No Comments July 16th, 2010 About… peter.stilgoe This author published 365 posts in this site. Sharepoint, InfoPath, K2, Nintex, Business Process Mapping, Business Intelligence, Automation, ECM, Document Management, Document Imaging, Internet Marketing & Online Business Consultant Email / MSN: pstilgoe@hotmail.com LinkedIn: Pete Stilgoe – Sharepoint Consultant […]

  2. Tom Berchenbriter · · Reply

    Id love a WSS3.0 WSSF3.0 WSS4.0 WSSF4.0 Comparison. Im almost done with my migration to WSSF4.0, but dont really think Im gaining anything… Please help.

  3. […] 2010'da değişen özellikleri kısaca gözden geçirmek ister misiniz? Ozaman buraya […]

  4. Hi Jackson,

    Thanks for this handy table. I have a client (in Australia) who would like to use it in a blog post. Can I have permission to reproduce the table? Of course, you will get attribution and a link to the original work in the body of the post. I just don’t see any point in reinventing the wheel when you’ve done such a fine job.

    Cheers,
    Sarah

    1. Sure.. Go ahead!

  5. Tom Berchenbriter · · Reply

    It would have really been useful having WSS vs MOSS 2010, and 2007 when we did our implementation, Im sure there are alot of others out there that dont know if 2010 WSS or the 2010 MOSS will be right for them… Microsoft did a pretty crappy job on the explinations of both, They couldnt even explain it over the phone… Maybe there is a better table out there now, but when we were shopping, we couldnt find this information…

  6. Hello Jackson,

    It could be interested to create and embed your comparison table with http://socialcompare.com/ platform: it enables you to create easily nice interactive and collaborative comparison table (with video, image, ratings, vote, yes/no….).

    Regards,
    Vanina

  7. Excellent work!!

  8. Somasekhar Akiri · · Reply

    Nice Table !! it helps me alot to find differences. Thanksssss…..

  9. […] Really Good Spreadsheet comparing earlier versions 2007 vs WSS 3.0 vs 2003 http://download.microsoft.com/download/1/d/c/1dc632e8-71e1-466f-8a2f-c940f1438e0a/SharePointProductsComparison.xls  (viahttps://jacksonc.wordpress.com/sharepoint-2010-vs-2007/) […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: