What has changed with Sharepoint 2010

Web Interface

• Integration of the Office Ribbon interface in the web
• Editing directly in the pages and items in the lists (no need to switch to bulk actions)
• Integration with Silverlight is out-of-the-box.
• Integration with Ajax, JQuery and other JavaScript libraries is out-of-the-box.

News

• BDC is now called the Business Connectivity Services (BCS) and supports reading and writing, yeah!
• Visio Services (similar to Excel Services), web-services that lets you put documents and diagrams in Visio Sharepoint, and also, allow configure workflows in Visio and import them to Sharepoint and vice versa.
• Sharepoint Desingn has a new editor now allows workflows and reuse workflows.
• LINQ is fully supported in SharePoint 2010 allowing a carry Join a SPListItemCollection without having to iterate through item by item to the map manually.

Requirements

• 64bit only, ouch! ... instances of SQL too :(
• The previous requirement to break some applications on MOSS 2007, MOSS SP2 in 2007 came a checker if our application can suffer an upgrade (call me psycho!!!) the version of Sharepoint. There is an article from Joel Oleson explains the process of this validation.

Sharepoint Designer (SPD)

• It took a treatment like "Dear i changed the Sharepoint Designer", and it has a new look, the menus disappeared and were substitutes for the Ribbon.
• The Workflow Editor is different, the dialog box was replaced by a workflow editor, a bit like the editor of Nintex.
• The SPD can now add the Workflows to Content Types, not just lists.
• Import Workflow Templates (awesome!)
• Creating Visio Services (similar to Excel Services but for Visio).

SDK

• Features include two new attributes UpgradeReceiverAssembly and UpgradeReceiverClass, supporting the new class method called SPFeature Upgrade, which allows you to make upgrades to our features, without being to install and uninstall the WSP and activate and deactivate Features every time we change something. To do this simply install the new Feature and use the Upgrade method:

SPFeature MyFeature = SPContext. Current.Site.Features [FEATURE_ID];
myFeature.Upgrade (false) / / boolean to force upgrade

When invoked the Upgrade method refers to the assembly described in the attribute UpgradeReceiverAssembly and we can control by code upgrade of our Featrues. As a requirement of the upgrade is necessary to be at least one version of the Feature is already installed, you can use the method SPSite.QueryFeatures to find out the Features that you can make an upgrade.

• Sharing Features, Settings and Services between sites in the same Site Collection. This is now possible through the class SPSiteSubscription, which indicates the items that the sites within a site collection can subscribe to each other.

• Solution Sandbox is a new feature that lets you create one Solution and deploy it to a site collection and run this solution in a single process without interfering with the other sites of the collection, is a way for us to try a new feature without breaking what was developed. This functionality is exposed by the class SPUserSolution. This solution has many limitations of resources (memory, CPU, etc.) and when these limits are exceeded the process is automatically "killed" by a Job that verifies the use of these solutions.
• To place an item on the menus of MOSS 2007 gives some work, now with the class SPUserCustomAction can add several items to the menu system Sharepoint.
• Use of Resource Types for multi-language, we can indicate the GlobalResources in the context of SharePoint, for example:

string title = SPContext. Current.Web.Titleresource.Value

• SPList.AppendDataTable is a new class that allows you to add a SPQuery results to a DataTable, which is quite effective in respect of the terms that do not merge the DataTable when we want to aggregate search results.