Book Image

Microsoft SharePoint 2010 development cookbook

By : Ed Musters
Book Image

Microsoft SharePoint 2010 development cookbook

By: Ed Musters

Overview of this book

<p>There is a heavy demand in the marketplace for SharePoint developers that you could take advantage of - if only you had the opportunity to acquire the relevant skills! But, SharePoint 2010 is a big old product with a steep learning curve &ndash; where do you begin? <br /><br />This book has been designed to take the experienced ASP.NET developer from &ldquo;beginner&rdquo; to &ldquo;professional&rdquo; SharePoint developer in the shortest amount of time. You will be productive on you very first SharePoint development assignment with the knowledge and skills that you learn here. You will have distilled the essence of the author&rsquo;s many years of training, and leading development teams in SharePoint. <br /><br />This book uncovers the most common &ldquo;pattern&rdquo; of typical SharePoint development tasks encountered in the real world and puts the topics in a logical order with detailed step-by-step recipes for you to follow. <br />The practical example given builds and flows throughout the chapters and topics. By the end of this book, you will be able to apply the concepts to the challenges ahead of you!</p>
Table of Contents (15 chapters)
Microsoft SharePoint 2010 Development Cookbook
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Retrieving SharePoint data using the list data service


I will have to admit something here first. I am not a "front end web developer" in the sense that I do not have anything beyond a working knowledge of HTML, CSS, JavaScript, and (increasingly importantly) jQuery. The web programming I do is typically with server-side controls and code behind in C#. As such, I do not personally have much call for consuming data that is not "natively" .NET, or which Visual Studio .NET abstracts away from me with references and proxy classes.

But I have witnessed wizards in jQuery, who have little to no knowledge of SharePoint or its object model, directly consume SharePoint data and the result is sheer UI magic. In fact, the UI platform may not even be Microsoft – nor need it be. These developers only ask that you provide the data in an "industry standard" format such as ATOM. And then query that data using industry standard REST. REST stands for Representational State Transfer and what it means is a query...