Client Object Model with the Open XML SDK

The Microsoft SharePoint Foundation 2010 managed client object model enables you to write applications that are based on the Microsoft .NET Framework that access SharePoint content from clients without installing code on the server that runs SharePoint Foundation 2010. 

The Open XML SDK 2.0 for Microsoft Office enables you to write applications to create, change, and query Open XML documents, the default document format for the Microsoft 2007 Office system and Microsoft Office 2010. By using these two technologies together you can write client-side applications that work with Open XML documents that are stored in document libraries.

more @ Using the SharePoint Foundation 2010 Managed Client Object Model with the Open SDK

asynchronous processing

using System;

using System.Collections.Generic;

using Microsoft.SharePoint.Client;

class Program

{

    static void Main(string[] args)

    {

        AsynchronousAccess asynchronousAccess = new AsynchronousAccess();

        asynchronousAccess.Run();

        Console.WriteLine("Before exiting Main");

        Console.WriteLine();

        Console.WriteLine("In a real application, the application can");

        Console.WriteLine("continue to be responsive to the user.");

        Console.WriteLine();

        Console.ReadKey();

    }

}

class AsynchronousAccess

{

    delegate void AsynchronousDelegate();

    public void Run()

    {

        Console.WriteLine("About to start a query that will take a long time.");

        Console.WriteLine();

        ClientContext clientContext =

            new ClientContext("http://intranet.contoso.com");

        ListCollection lists = clientContext.Web.Lists;

        IEnumerable<List> newListCollection = clientContext.LoadQuery(

            lists.Include(

                list => list.Title));

        AsynchronousDelegate executeQueryAsynchronously =

            new AsynchronousDelegate(clientContext.ExecuteQuery);

        executeQueryAsynchronously.BeginInvoke(

            arg =>

            {

                clientContext.ExecuteQuery();

                Console.WriteLine("Long running query completed.");

                foreach (List list in newListCollection)

                    Console.WriteLine("Title: {0}", list.Title);

            }, null);

    }

}

How the Client-Side Object Model Works

How the Client-Side Object Model Works

An application that uses SharePoint content interacts with the API in several ways—call methods and get the return values, pass a Collaborative Application Markup Language (CAML) query and get the results, and set or get properties. After you use the API to perform a specific task the SharePoint Foundation 2010 managed client object model bundles up these uses of the API into XML and sends it to the server that runs SharePoint Foundation. 

The server receives this request, and makes appropriate calls into the object model on the server, collects the responses, forms them into JavaScript Object Notation (JSON), and sends that JSON back to the SharePoint Foundation 2010 managed client object model. The client object model parses the JSON and presents the results to the application as .NET Framework objects (or JavaScript objects for JavaScript). The following diagram shows these interactions.

It is important to be aware that you control when the SharePoint Foundation 2010 managed client object model starts to send the XML to the server and receives the JSON back from the server.

more @ Client-Side Object Model

Client Class Library

Name	Description
Microsoft.SharePoint.Client	Core namespace that provides types and members for working with SharePoint Foundation Web sites, list data, and users within a site collection.
Microsoft.SharePoint.Client.Utilities	Provides types and members for encoding strings, for working with security principals, and for performing specific utilities tasks.
Microsoft.SharePoint.Client.WebParts	Provides types and members for managing Web Parts within Web Parts pages.
Microsoft.SharePoint.Client.Workflow	Provides types and members for managing workflow templates and workflow associations.

The members of the Microsoft.SharePoint.Client.Application namespace are reserved for internal use and not intended to be used directly from your code.

Client-side classes and server-side equivalents

Client	Server
ClientContext	SPContext
Site	SPSite
Web	SPWeb
List	SPList
ListItem	SPListItem
Field	SPField

Notice that the SharePoint Foundation 2010 managed client object model uses the same legacy naming pattern for site collections and sites as the server object model. 

The Site class represents site collections, and the Web class represents sites. 

My preference for using these classes is to name the variables so that the variable name indicates whether it is a site collection or a site, even though you must use the Site and Web classes to declare them.

The following example shows how name variables.

C#

ClientContext clientContext = new ClientContext(siteUrl);

Site siteCollection = clientContext.Site;

Web site = clientContext.Web;

Namespaces in the JavaScript Object Model

==========================================================================
Namespace                                                                         JavaScript File

==========================================================================

CUI Namespace                                                                CUI.js, SP.UI.Rte.js

CUI.Controls Namespace                                              CUI.js

CUI.Page Namespace                                                     CUI.js, SP.UI.Rte.js

SP Namespace                                                                  SP.Core.js, SP.js, SP.Ribbon.js, SP.Runtime.js

SP.ListOperation Namespace                                       SP.Core.js

SP.Ribbon Namespace                                                  SP.Ribbon.js

SP.Ribbon.PageState Namespace                              SP.Ribbon.js

SP.UI Namespace                                                            SP.Core.js, SP.js, SP.UI.Dialog.js

SP.Utilities Namespace                                                  SP.Core.js, SP.js, SP.Exp.js

SP.WebParts Namespace                                              SP.js

SP.Workflow Namespace                                              SP.js

==========================================================================

Calendar view for a list

Create a calendar view for an existing list

SharePoint 2010 - more info

SharePoint 2007

SharePoint 2007 

More About Calendar SharePoint 2010

Calendar Colour Coding in SharePoint

Calendar Overlay & Color Options

David Lozzi.com

Overlay and Color Options

SharePoint cool sites...

Resultado de testes na imagem abaixo:

Calendar Reminder

How to : Add Reminder to SharePoint 2010 Calendar

http://kmlsp.wordpress.com/2012/03/13/how-to-add-reminder-to-a-calendar/

jQuery Library for SharePoint Web Services

SPServices

Exemplo:

Slider

LINQ to SharePoint Provider

The gateway class for the LINQ to SharePoint provider is Microsoft.SharePoint.Linq.DataContext which represents the data of a SharePoint Foundation Web site. 

It is parallel in use and function to the System.Data.Linq.DataContext class in the LINQ to SQL provider. 

Just as the latter class has a GetTable() method that returns a Table<TEntity> object that implements System.Linq.IQueryable<T>, so too, the Microsoft.SharePoint.Linq.DataContext class has a GetList<T>method that returns an EntityList<TEntity> class that implements System.Linq.IQueryable<T>. 

It is objects of type EntityList<TEntity> that are queried.

The following is an example of the use of LINQ to query SharePoint Foundation.

// Get DataContext from page context
DataContext data = new DataContext(SPContext.Current.Web.Url);

// Get the SharePoint list
EntityList<Customer> Customers = data.GetList<Customer>("Customers");

// Query for customers from London
var londonCustomers = from customer in Customers
                      where customer.City == "London"
                      select customer;

foreach (var londonCust in londonCustomers)
{
    Console.Writeline("id = {0}, City = {1}", 
                      londonCust.CustomerId, 
                      londonCust.City);
}

The following is an example of using LINQ to add an item to a SharePoint Foundation list.
// Get DataContext from page context
DataContext data = new DataContext(SPContext.Current.Web.Url);

// Get the SharePoint list
EntityList<Customer> Customers = data.GetList<Customer>("Customers");

// Create the item to be added
Customer newCustomer = new Customer() { CustomerId=36, City=”Madrid” };

// Mark the item to be added on the next call of Submit
Customers.InsertOnSubmit(newCustomer);

// Submit all changes
data.SubmitChanges();

SharePoint 2010

Todo material foi compilado em palestras e são informações valiosas sobre SharePoint 2010.