SharePoint 2010 is in many ways superior to its predecessor, the 2007 version. Both for the user and the developer, the 2010 version offers services and tools out of the box (OOTB) that were sought after in the previous releases.
1. Language Integrated Query (LINQ)
With the new LINQ provider, a relational database table can be mapped to .NET Objects and operations are converted to the correct SharePoint operations using the native CAML language (which is supported by SharePoint).
2. Lists
Users of the 2007 version used to say that everything in SharePoint is a list. They are just as essential and critical in 2010. They now have new scale limits, XSLT views, list relationships that support cascade deletes and updates and formula validation (better than in the 2007 version). Also, the new External Data List allows the presentation and manipulation of data from external sources (e.g. from databases or web services)
3. Business Connectivity Services (BCS)
The old Business Data Catalogue (BDC) has been revamped. It now supports read/write operations, supports the Windows Communication Foundation (WCF) and APIs on both the server and the client so that offline work on Line of Business (LOB) data can be supported. The data is then synced back to the server.
4. Silverlight
Some courageous folks had attempted integrating Silverlight into SharePoint 2007 installations. The 2010 version sports a drag and drop Silverlight web part that can host any Silverlight application that it is pointed to. The web part also used XAML themes so that it can be customised to fit with the rest of the webpage. It also supports a preview image that will be displayed before the “play” button is pushed.
5. Client Object Model (COM)
Long are the times when programmers had to invoke web services to achieve the desired operation. The new COM provides a typesafe environment that works with the Intellisense in Visual Studio.
6. New Protocols and Standards
SharePoint 2010 supports the new Web 2.0 Protocols. Representational State Transfer (REST), Asynchronous JavaScript + XML (AJAX), JavaScript Object Notation (JSON), AtomSub/Pub. Standards validation is supported by Content Management Interoperability Services (CMIS). This way one can achieve mash-ups between systems on SharePoint or interoperability between systems.
7. Sandbox Solutions
In 2007, safety precautions would require the developer to implement Code Access Security (CAS) to ensure that malicious code is not injected into the installation (since all code had to be in the global assembly cache – GAC). In 2010, Sandbox solutions are supported. These are hosted inside a secure environment on SharePoint and resources used by these applications are governed by the system. Although only a subset of SharePoint is reachable through Sandbox solutions, they are valuable since they ensure stability of the system.
8. SharePoint Designer (SPD)
Most developers don’t even want to hear about the SharePoint Designer (SPD), which is something I never quite understood. I honestly adored the 2007 Designer and with the new version, I’m loving it even more. The new SPD supports type browsing (instead of the old site hierarchy), introduces a new entity modeller to simplify BCS connectivity to backend services and model the backend data into SharePoint and also, provides much better workflow solutions that import Visio diagrams (business data is then added to the diagrams and the status of the workflow can be displayed graphically). A nice thing about workflows based on Visio diagrams is that the status of the workflow will be displayed by using the Visio diagram itself through the Visio Services.
The new SharePoint Designer fully supports Infopath for creating workflow forms. ASP forms can be replaced by better looking InfoPath forms that provide more functionality (like advanced logic and data connectivity).
Also, please do note that, the new SPD is free of charge =D
9. More Supported Services
SharePoint 2007 supported Excel and InfoPath Form services. SharePoint 2010 also supports Visio and Access services. Visio diagrams can be designed and be connected to backend systems for visualisation of data and then be posted on SharePoint. SharePoint will render the read-only diagram, with the data connectivity. Access services allow MS Access applications to become web solutions. Access forms can be moved to web-based forms for a complete transformation. Word services has also been included with the new iteration of SharePoint and as such, developers don’t have to program against OpenXML. There are now server APIs that provide conversions and assembly.
10. InfoPath Form Services updates
In 2010, InfoPath forms can replace the standard ASP list forms. This allows for richer applications that support business logic and data connectivity that work in the new Workspace. Mobile forms are also supported for solutions that need be reachable through mobile devices.
11. Visual Studio
The Server Explorer allows browsing the SharePoint environment (quick access to lists, libraries, content types, etc). The visual web part designer makes the development of web parts easier (no more hand coded html). Visual Studio integrates SharePoint development into a team development environment with support for Team Foundation Server and easy deployment using the new Web Solution Package format. Also, it supports the Web Solution Package format (WSP).
12. Web Solution Packages (WSP)
The Web Solution Package (WSP) is supported across all tools so that sites can be exported through the browser, designer and visual studio. Solutions can quickly be upgraded or downgraded between the tools. SharePoint Online also supports this format so that solutions can be easily moved to the cloud.
13. Developer Dashboard
SP2010 introduces the new developer dashboard that allows the developer to see all the calls -native and custom- made on a page right inside from the user interface.
14. Social Computing
SP2010 supports enhanced blogs and wikis, tagging, ratings, etc. Social computing and Enterprise Content Management converge so that social computing is the bottom-up technology driven by user input and ECM being the top-down technology what helps with compliance in the social environment. Social tagging, called folksonomy, is actually an open term set of corporate taxonomy. Activity feeds like the ones in FaceBook and twitter are also supported, as is micro blogging, a 140-char post like tweeting. For example, if someone works on a document that a user is interested in, that information appears on the user’s activity feed. An organisational chart is also provided so that a user can browse the relations between employees. This is actually a Silverlight browser, which saves on postbacks to the server. SP2010 also offers an OOTB tag cloud web part.
15. Outlook Social Newsfeeds
The new Outlook integrates with SharePoint and other social platforms, such as FaceBook, and surfaces more information about the users, such as photos, activity feeds, previous conversations and even previous instant messaging sessions. Outlook also surfaces keywords, based on a user’s communications (approvable by the user), which are searchable and stored on a user’s profile. This makes connecting to experts in an organisation much easier.
16. New, based on FAST, Search
The new Search feature is first of all extensible (as opposed to the one in SP2007 which was sealed) and supports wildcards, suffix matchings, grouping of query terms, logical operations, etc. The new Search also provides item preview and filtering by multiple criteria. People search now uses Phonetic Search. That means that if a name sounds like the one typed in the search box, it will be displayed in the result even if it is actually spelt otherwise. The People Search results also displayed the expertise and place in the organisational hierarchy of the
17. Location based metadata
Items posted in a specific location have their metadata filled automatically.
18. Document Routing
A document can be submitted to SharePoint, in the case where the user does not know where it should be placed according to the enterprise taxonomy, and the document will be routed to the appropriate location automatically.
19. Unique Document ID
Documents now have unique document ID’s so that a user can search for a document by its ID. The ID never changes, so that if a document is moved, the user can still retrieve it by its ID.
20. Taxonomy Services
Different taxonomy hierarchies are supported (for use with different scenarios). Also, the taxonomy service is an enterprise-wide service so that it can be used across site collections. It also supports synonyms and the Office clients ship with controls that understand the term sets in order to
21. Document Sets
One of the great things vastly improved with SP2010, as far as Enterprise Content Management (ECM) goes, is the introduction of document sets. In SP2010, we can create document sets that are made up by Word, Excel, PowerPoint, etc. files, onto which, we can perform workflows or check them out altogether, set metadata and give it a user interface, etc. Document management can be performed on the set as a whole or on the separate documents that make up the set. Versioning on the set is separate of the distinct versions of the documents that make up the set and document sets can be exported as wholes in zip format files.
22. Content Management Interoperability Services (CMIS)
CMIS is a new standard that provides interoperability between various content management providers, beyond that of simple create, read, update delete (CRUDE) functions. Check-in and check-out are also provided and various other higher level semantics. These are all possible through Representation State Transfer (REST) APIs.
23. Multistage disposition
With SharePoint 2010, it is possible to have various rules that define disposition of documents. For example, documents can be disposed of every 5 years but go under review every 1 year. Or perhaps, digitally signed documents can be disposed of every 10 years.
24. In-place record management.
With SharePoint 2010, we can apply record management policies to content that is not placed in the Content Centre but instead, it is retained in its original location.
25. Enhanced Page Libraries
In SharePoint 2010, we can finally have folder in the pages library. Also, thanks to content routing, content can be automatically placed in the appropriate folders.
26. Better media files support
In SharePoint 2010, media files, including audio and video, are supported so that their properties (frame rate, dimensions, preview image, copyrights, etc) are supported to. Workflows and other SharePoint functionality can work against these. Also, bit rate throttling has been enabled in order to correct the speed based on the data rate of the original video file. Content rating, provided by the Digital Assets Management (DAM), allows users to rate media files (just like any other file) so that only the highest ranking files will appear in searches, etc. The metadata of media files are automatically filled when the files are being uploaded.
27. Remote Binary Large Object (BLOB) Storage
SharePoint supports remote Binary Large Object (BLOB) storage but requires the drivers from the BLOB provider. Once the drivers have been acquired, SharePoint allows us to move the BLOB from the SQL to the location that the provider supports. SharePoint will maintain transactional consistency between the metadata stored in the SQL Server and the BLOB storage. This way, we can move BLOBs out of the expensive SQL storage to cheaper solutions.
28. Workflows
One of the great features of SharePoint 2007 has been greatly improved by making the OOtB workflows modifiable. In 2007, those were sealed but now, they can be modified by both the SharePoint Designer and the Visual Studio (in case we need to edit or add a step, for example). Furthermore, workflows can now run against external data that has surfaced into SharePoint though the Business Connectivity Services (BCS). Workflows can also run against folders or against data that is stored in external Line of Business systems.
29. SharePoint Workspace (the old Groove)
The SharePoint Workspace has been re-architected to be a rich SharePoint client. It allows users to synchronise SharePoint data, like lists and libraries, even LOB data, and work with these offline. Once online again, the data will be synchronised back to the LOB system. This is a great option for slower internet connections as the SharePoint Workspace (SPW) is primarily intended for offline use.
Powered by Zoundry Raven