MOSS 2007 vs MOSS 2010
In this article, we are going to see technical preview on SharePoint 2010, MOSS 2007 vs MOSS 2010. Architectural difference, Limitations.
Key Features
- New User Interface including new Ribbon
- Web Edit
- Silverlight Web Part
- Rich Theming
- Multiple Browser Support
- Visio Services
- SharePoint Designer
- Business Connectivity Services
- SharePoint Workspace
- Rich Media Support
Administration Improvements
- Streamlined Central Administration
- Best Practices Analyzer
- Unified Logging Database
- Resource throttling for large lists and libraries
Development Improvements
- Visual Studio 2010 Tools including a Package Designer and Web Part Editor
- LINQ for SharePoint
- Developer Dashboard: Page-level debugging/trace output
- Business Connectivity Services (BCS) replaces Business Data Catalog (BDC) with SharePoint Designer 2010 and Visual Studio 2010 will provide BCS-specific tooling.
- Client Object Model (OM) is a new SharePoint API that runs on the client and can be called from JavaScript, .NET, or Silverlight
Architectural Difference
MOSS 2007 Architecture:
MOSS 2010 Architecture:
Comparison
Limitations
SharePoint 2010 has hardware and other limitations:
- SharePoint 2010 will only be available in a 64-bit version. This change is not limited to servers. Developers running on 32-bit hardware will need new machines.
- SharePoint 2010 will require a 64-bit version of SQL Server 2005 or 2008 (2000 is no longer supported).
- Not all applications written for SharePoint 2007 will work in 2010. Certain APIs will be no longer be available. Others will be deprecated.
- The basic flow for many tasks as changed. That, coupled with the laundry list of productivity-enhancing features means that any 2010 deployment should be accompanied by training for users, administrators, and developers.
