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

Creating new Site Columns


Before we can create Content Types, we need to define all of the individual Site Columns that will appear (ultimately) in our SharePoint lists. First, please look at the rather extensive set of Site Columns you get "out-of-the-box" and please feel free to reuse them instead of duplicating something similar.

Note

The Site Columns available will depend first on the version of SharePoint you have available – Foundation, Standard, or Enterprise. Secondly, on which features (Standard, Enterprise, and Publishing) are enabled at the Site Collection and Site level.

In our case, we will be defining a document library to hold our proposals. We are going to define the following additional Site Columns that we require:

  • Proposal Amount: Number

  • Proposal Client: Single line of text

  • Proposal Type: Choice field

Note

For simplicity of the example, the client is a single line of text. This could have been another long list (the client list) and we could then define a "lookup" to be able to...