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

Working with the .NET Client Object Model


To access data from outside of the SharePoint world was a tedious proposition in the previous version of SharePoint. I personally found the "lists web service" lacking, and let us leave it at that. The best and often quickest solution was to use something I was very familiar with – the SharePoint object model – to access lists and libraries. But of course you could not run that on the client (for example, a Windows Forms or Windows Presentation Foundation application). Your SPList code had to run physically on the SharePoint server. So we wrote our own web services (ASMX) that ran exactly the friendly and easy-to-write code we wanted, then packaged it up for deployment alongside SharePoint's other web services (in the 12/ISAPI folder, mapped to _vit_bin virtual directory). It was an entirely new level of fun to AJAX-enable first SharePoint and then your web services so that you could use an asynchronous execution model and avoid the usual postbacks...