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

Features and Solutions


If you have professionally developed any type of application, then you must have had the requirement to "deploy" it. For example, if you are developing a Windows (desktop) application, you may have been asked to create a setup.exe for it – which in Visual Studio is a deployment project. If you are a web application developer, you can similarly add a "web setup project" and/or deploy your files in a CAB file (a special type of ZIP/compressed) file. Or perhaps you have experience with using MSI (windows installer) files. Regardless, when it is time to hand off your application to others you must "package" it for deployment.

SharePoint at its heart is an ASP.NET web application, so SharePoint understands special installer files called Solutions (creative name, right?). SharePoint solution files have the extension .wsp and are simply in CAB (compressed) format. The great news is that Visual Studio 2010 will automatically "package" your SharePoint customizations in WSP...