APIs para SharePoint Online

Editor's Notes

• #11: Ruta de instalación de los ensamblados: C:\Program Files\Common Files\microsoft shared\Web Server Extensions y en la GAC
• #15: Ejemplos de parámetros: el Guid de una lista
• #18: To understand how to use OData as a developer, you must understand how OData URIs are constructed. Each URI has three significant parts, The first part of the URI is the Service root URI which points to a site on the Internet and a path to an entry point such as a .svc file. The next part of the URI is the Resource path which identifies a specific object such as a site, a collection (e.g list) or an entry (e.g. item). The final part of the URI are the optional query string parameters that allow you to request special processing instructions such as filtering and sorting.
• #19: This is a READ sample. The other CRUD operations follow.
• #20: Response data format selected with ACCEPT header XML can be easier to deal with from managed code. To get ATOM XML response use "application/atom+xml" JSON is easier to deal with when using JavaScript. To get JSON response use "application/json" When you run REST-based queries against SharePoint 2013 sites, you have the option of having the data returned as either XML in the ATOM format or JSON (JavaScript Object Notation). The default behavior is to return XML but you can change this default behavior to return JSON by including the ACCEPT header with a value of "application/json". If you include the ACCEPT header with an explicit value of "application/atom+xml", this has the same result as the default behavior in that the results are returned as ATOM-based XML. As a general rule of thumb, it is easier to deal with XML-based results when writing managed code such as C# or VB.NET. Likewise, it is easier to deal with JSON results when programming with JavaScript. Note that jQuery makes dealing with JSON results even easier.
• #21: SharePoint 2013 (and previous versions) uses a client side “token” to validate posts back to SharePoint to prevent attacks where the user might be tricked into posting data back to the server. This token is known by many names;form digest or message digest or request digest. The token is unique to a user and a site and is only valid for a (configurable) limited time.
• #24: Modificar con parte específica de SPO -------------------------------------------------- If you are making REST calls into SharePoint 2013 using C# or VB.NET, there are a few tips to make things easier. First, .NET 4.0 added a two new classes named HttpWebRequest and HttpWebResponse which provide a few conveniences not offered by their base classes WebRequest and WebResponse. For example, there is a stongly-typed Accept property on the HttpWebRequest object that allows you to set the ACCEPT header. When it's time to retrieve data values from elements within an XML document, it's time to abandon older XML APIs such as XMLReader in favor of Linq to XML and the XDocument class. Retrieving data from an XML document using the Descendants property of an XDocument object as shown above makes dealing with nested elements and XML namespaces so much easier.
• #25: Modificar con parte específica de SPO -------------------------------------------------- If you are making REST calls into SharePoint 2013 using C# or VB.NET, there are a few tips to make things easier. First, .NET 4.0 added a two new classes named HttpWebRequest and HttpWebResponse which provide a few conveniences not offered by their base classes WebRequest and WebResponse. For example, there is a stongly-typed Accept property on the HttpWebRequest object that allows you to set the ACCEPT header. When it's time to retrieve data values from elements within an XML document, it's time to abandon older XML APIs such as XMLReader in favor of Linq to XML and the XDocument class. Retrieving data from an XML document using the Descendants property of an XDocument object as shown above makes dealing with nested elements and XML namespaces so much easier.
• #26: Modificar con parte específica de SPO y funcionando… -------------------------------------------------- This slide shows the code which demonstrates creating a new list using client-side C# code which uses the new REST entry point. The first task it to parse together URL to point to lists collection which is _api/web/lists. The next task is to add the X-RequestDigest header which includes the value of the form digest. This example also sets the ContentType header to a value of application/atom+xml to tell SharePoint it is passing XML as opposed to JSON. Next, you must create an XML document that contains an Entry as defined by ATOM and conforms to the structure used by SharePoint 2013. The last task is to execute the request using an HTTP POST operation.
• #27: API REST desde PowerShell y desde .NET
• #35: Demo de NAPA
• #37: Load() and LoadQuery() inicializan las propiedades. ExecuteQuery() realiza la llamada al servidor. Podemos tener excepciones de tipo PropertyOrFieldNotInitializedException.
• #38: This is a READ sample. The other CRUD operations follow.
• #39:  SP 2013 Client Browser CAML Designer Scripts PowerShell: El de Obtener Sitios de una Colección, el de Flujos
• #43: Transform your code - Providing App Model Patterns for common Full Trust Code scenarios 60+ Visual Studio projects Common scenarios