SharePoint 2010 Developer Overview:
Original Post Here: -->
- The trick is that Visual Studio is 32-bit and SharePoint is 64-bit, so if you want Visual Studio to execute SharePoint operations, you need to use a special SharePointCommand type that will marshal the code for you for execution in a 64-bit thread. The Client OM would be a simpler option if you don't need to elevate permissions.
 - SharePoint 2010 can be installed on Windows 7 or Vista SP1
 - Windows SharePoint Server is now SharePoint Foundation Server
 - Still it runs on 64bit
 
- Package and Deploy
 - Can view SharePoint site via the Server Explorer
 - TFS integration
 - Sandbox support, WSP Import (nice)
 - BDC becomes BCS (Business Connectivity Services)
 - Both SPD and Visual Studio 2010 read and write same, i.e. if you send any .wsp package it will pick it up.
 - All OOB web parts in SP2010 are public and no longer sealed. So now devs can extend all existing web parts
 
- Will remain free
 - SharePoint Designer 2010 will not work with SharePoint 2007.
 - It is a completely new runtime.
 - FrontPage functionality hangovers either hidden or removed.
 - Workflow Designer
 - SharePoint Designer 2010 keeps tracks of every single change, so that means versioning is always on.
 - It also does not allow you to customize (or unghost) webpart pages by default. You have to open up the page in Advanced Edit Mode.
 - Skewer Click: It's new feature by dragging it from the ribbon onto a cell in the DVWP and you will be able to see all of the elements parents
 
- Can create relationships between lists.
 - This is piggy backing on SQL functionality
 - Validation support, Excel like formulas
 - Lookup to multiple columns,
 - Automatically create indexes where they make sense (for example on lookups)
 - No need to worry for 2,000 Item Limit, Example 220,000 item lists.
 - Views will use XSLT.
 - Throttling will block queries that are made for large numbers of items (configurable)
 
- JQuery is now hosted on SharePoint 2010.
 - JQuery.sparklines.js plugin is included which will allows you to create contextually sensitive charts and graphs.
 - JQuery plugin for Firebug called FireQuery is being used.
 - A “sparklines” class is added to each row of the DVWP to be able to add the sparklines plugin to show a line graph next to each project item based upon its sequence column. The sequence column just as a comma delimited series of integers.
 
- REST is not a protocol, it's not a standard, it's an architectural design.
 - It's a simple guidance that builds systems that focus on a resource centric approach.
 - Data organized as addressable resources. Uniform interface to act on them.
 
- Server Object Model which is already present in 2007
 - New: Client OM –> Runs on the desktop
 - New: REST API’s –> ATOM response
 - New: LINQ and all LINQ goodness
 - Supports Joins and Projections
 - If you want to work with relationships between items, REST and LINQ are much easier to use than the OM.
 - Use Server Object Model and LINQ to SharePoint when you are developing on the server.
 - Use Client Object Model and REST when running the code on a remote computer.
 - Will dramatically reduce run time errors, moving them to compile time
 
- Site collection administrator can put a limit on the query block i.e. x number to be blocked
 - Developer can override the querythrottlingblock to retrieve more items from the server.
 
- Pagination plays a distinct role so that the data is filtered on the server, not on the client side anymore.
 
Original Post Here: -->
No comments:
Post a Comment