[SP2010] Development Changes

Rate this item
(0 votes)
  1. Upgradable features – can be easily upgrade via code and API available to query features
  2. Sandbox isolation – you can deploy features to site collections in “Sandbox” mode, and solution won’t affect other sites. You can deploy a Web Part to a SharePoint site and have it run in the context of that site either in an on-premises instance of SharePoint or in the cloud using the hosted version of SharePoint. The limitation is by site collection scope.
  3. Customizable upload page – you can use “CustomUploadPage” class to create your own _layouts\upload.aspx
  4. New types by namespace in Microsoft SharePoint Server "14 (add picture)
  5. The new Microsoft.SharePoint.Linq namespace, which defines a LINQ to SharePoint provider that translates LINQ queries into Collaborative Application Markup Language
  6. Standardized Windows SharePoint Package (WSP) package.
  7. The Client Object Model enables to access SharePoint objects through a referenced DLL as opposed to Web service calls
  8. Save site as WSP – is helpful for prototyping
  9. You should recompile custom code written for Office SharePoint Server 2007 if your solution includes a feature receiver that implements FeatureInstalled, FeatureUninstalling, FeatureActivated, and FeatureDeactivating
  10. Microsoft SharePoint Server 2010 contains more than 1,500 deprecated types, most in the Microsoft.SharePoint.Portal
  11. User Code Execution Service - Microsoft SharePoint Server 2010 implements a capability to securely host custom solutions and executable code that comes from customers of the system.  It provides better controls for the security of execution of custom code, as well as mechanisms to monitor and control the usage of resources by that code.
    One requirement of these mechanisms is to move the execution of the code to separate processes and separate servers, to provide better layers of isolation and monitoring.  Therefore, two roles are defined in a user code execution process: a front-end Web server which initiates requests to run user code on behalf of a user, and a code execution back end service which fulfills the execution request.  Communication between these servers is specified via the User Code Execution Protocol specification ([MS-SPPTC]).
  12. Thee object models - managet .NET API, Silverlight Object Model, JavaScript & ECMAScript library  http://www.tonstegeman.com/Blog/Lists/Posts/Post.aspx?ID=118

Official Info:

  1. Namespaces http://msdn.microsoft.com/en-us/library/ee556849(office.14).aspx
  2. Class Library and Web Services http://msdn.microsoft.com/en-us/library/ee556847(office.14).aspx

Samples:

Building a SharePoint 2010 Service Application http://sharepointsolutions.blogspot.com/2009/10/updated-building-sharepoint-2010.html

Using the SharePoint Foundation 2010 Managed Client Object Model http://msdn.microsoft.com/en-us/library/ee857094(office.14).aspx

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.