SharePoint Connections 2010, Den Haag, 28 September 2010
Session: Creating a Rich Business Application with the Managed Client Object Models in SharePoint 2010 (MDV01)
Speaker: Andrew Connell (http://www.andreconnell.com/blog)
- This session contained mostly things that apply to SharePoint 2010 but there were also remarks about SharePoint 2007
- Important points
- Overview of building Rich Internet Applications (RIA)
- Options we have in SharePoint 2007
- Options we have in SharePoint 2010
- Riche Internet Applications (RIA)
- As a definition, RIA engages client-side solutions, meaning AJAX, Flash, Silverlight
- In SharePoint 2007 you might need extra setup and config
- In SharePoint 2010 it’s out of the box + extra connection points from client applications.
- Security trimming is present in both versions -> nothing to do for the developers
- Option we have for RIA In SharePoint 2007:
- ASP.NET 2.0 (. ASMX web services)
- WCF (.SVC) technically not supported
- Silverlights v3 which requires ASP.NET 3.5 and a lot of edits in web.config
- Options we have for RIA in SharePoint 2010
- Better consume & create web services (ASP.NET & WCF)
- Client Object Model
- A lot more interaction is possible with the site collection
- Extends the SharePoint object model to Silverlight
- Enables developers to work with familiar objects rather then web services
- It’s centered on the ClientContext – handles communication with SharePoint sites.
- Sends commands to SharePoint (ExecuteQueryAsync(success,fail))
- Using it requires 2 references:
- Microsoft.SharePoint.Client.Silverlight.dll; (this includes .NET Client OM API’s
- Microsoft.SharePoint.Client.Silverlight.Runtime.dll (does all the communication to SHAREPOINT server back and forth); (to be found in […]/14/templates/layouts/ClientBin/)
- LINQ is only working on servers side…on client side you will need CAML query!..CAML is dead..long live CAML J
- Works only using async communication
- OData/WCF Data Services / RESTful services
- Very easy to read/write data to lists and sites.
- It does not allow changes of structure, permissions, or navigation like within the client model.
- OData is an open protocol founded on REST principals
- WCF Data Services is the Microsoft implementation of OData open protocol
- Does not work out of the box!! J To make it work you need WCF Data Service Update for .NET 3.5 SP1
- OBS: Dataaccesspolicy.xml defines who can call which service (normally found in the root of the Inet application)
- Sandbox Solutions
- Code deployed by non-admins via browser
- Runs in an isolated environment
Advertisement
[...] Creating a Rich Business Application with the Managed Client Object Models in SharePoint 2010 (MDV01… [...]