SharePoint 2010 as a Development Platform

By Joerg Krause , Martin Dring , Christian Langhirt , Bernd Pehlke , Alexander Sterff

SharePoint 2010 as a Development Platform Cover Image

This book takes an in-depth, all-encompassing approach to programming concepts, the extensibility interfaces, and how to embrace SharePoint as a toolkit full of features available to web developers.

Full Description

  • ISBN13: 978-1-4302-2706-9
  • 1164 Pages
  • User Level: Intermediate to Advanced
  • Publication Date: June 29, 2010
  • Available eBook Formats: EPUB, MOBI, PDF
  • Print Book Price: $54.99
  • eBook Price: $38.99
Buy eBook Buy Print Book Add to Wishlist

Related Titles

Full Description

SharePoint is gaining recognition as a full-fledged application server with many features and enhancements that specifically allow non-developers to create sophisticated intranet sites. However, with the 2010 release, Microsoft’s SharePoint increasingly becomes a compelling development platform. The strong application programming interface (API), its highly extensible nature, and its foundation on the underlying .NET Framework all generate “the perfect storm” to make it one of the most powerful web development platforms available.

However, with power comes complexity. The wide range of usage scenarios make it difficult for developers to grasp the full ability of this next-generation platform. This book takes an in-depth, all-encompassing approach to programming concepts, the extensibility interfaces, and how to embrace SharePoint as a toolkit full of features available to web developers.

  • Take an in-depth look into the internals of SharePoint.
  • Create sophisticated applications using SharePoint controls and databases.
  • Understand the API and use in conjunction with ASP.NET to extend SharePoint.

SharePoint is more than a portal and more than an intranet. Harness its capabilities and put it to work for you.

What you’ll learn

  • The hierarchy of SharePoint’s API
  • How to create rich, extensible, and broad SharePoint applications
  • How to use SharePoint’s internals
  • How to approach SharePoint as an open toolkit rather than a closed, intranet-only model
  • How to take advantage of SharePoint’s extensibility and customize its behavior

Who this book is for

This book is for ASP.NET developers who want to create applications using SharePoint as a platform. It’s also for users of SharePoint Designer that want to professionalize their development work.

Table of Contents

Table of Contents

  1. Developer Basics  
  2. Architecture 
  3. Accessing the API 
  4. Data Access  
  5. External Data Access 
  6. Web Parts 
  7. Templates  
  8. Application Techniques  
  9. Solution Deployment 
  10. Extending the User Interface  
  11. Using Web Controls 
  12. Client Programming 
  13. Integrating Silverlight 
  14. Integrating Charts and Maps  
  15. Forms Services and InfoPath
  16. Workflows
  17. Administrative Tasks 
  18. Enterprise Features 
Source Code/Downloads

Downloads are available to accompany this book.

Your operating system can likely extract zipped downloads automatically, but you may require software such as WinZip for PC, or StuffIt on a Mac.


If you think that you've found an error in this book, please let us know about it. You will find any confirmed erratum below, so you can check if your concern has already been addressed.

* Required Fields

On page 357:

In Listing 6-32, you are missing:

Using System.Linq;
Using System.Runtime,InteropServices;

On page 476:

On Method GetItemsByQuery() the following line:

query.RowLimit = Convert.ToUInt32(Constants.RowLimit);

Should read instead:

query.RowLimit = Convert.ToUInt32(Constants.PaginationThreshold);

On page 727:
The description of the showMaximized option is wrong.

The description should say that if the option is true, the dialog will be displayed maximized by default.

On page 728:
There is a function named commitPopupAndRedirect that is listed on this page. This function does not exist in SharePoint 2010.

On page 728 and 729:
The description for the navigateParent is wrong. It redirects the parent page to the specified URL. As such, the method does take a prameter with is the URL of the page to navigate to.