SharePoint 2010: How to Set Up a Development Environment with Windows Server 2008 and SQL Server 2008
|
Introduction
When you create or customize SharePoint 2010 solutions, it is usually best to develop the solution on a local computer where Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010 is installed: this article describes how to install a development environment with Microsoft SharePoint 2010 and Microsoft Visual Studio 2010. The development environment that you create by using these instructions will support SharePoint 2010 farm installations and is almost equal to a SharePoint 2010 production environment, because it will use Windows Server 2008 features like Active Directory and a robust DMBS server like SQL Server 2008. These instructions enable you to get started with an environment that is specifically suited to developing SharePoint custom solutions.
If you want to set up a simpler development environment that allows you to build SharePoint 2010 solutions without installing a "close to real" server environment (for example, if you want to use a client Windows version or if you do not have a SQL Server installation), you can read the article "SharePoint 2010: How to Set Up a Development Environment".
Hardware and Software Requirements
Creating a "close to production" SharePoint development environment imposes high hardware and software requirements: the development machine will host the web front end, the database server and the development tools provided by Microsoft Visual Studio, thus having a serious impact on the system's performance. According to the TechNet Library's "Hardware and software requirements (SharePoint Server 2010)" document, you'll need a machine with the following characteristics
- 64 bit (SharePoint 2010 is a 64 bit program, thus requiring a 64 bit operating system running on a 64 bit CPU), four cores CPU
- 8 or 16 GB of RAM
- at least 80 GB of free space on the hard disk
All the required software programs needed to set up the environment are available as trial versions that can be downloaded for free from the following links:
- Windows Server 2008 R2 Evaluation (180 days): http://www.microsoft.com/en-us/download/details.aspx?id=11093
- Microsoft® SQL Server 2008 R2 Evaluation - Trial Experience for Developers: http://www.microsoft.com/en-us/download/details.aspx?id=8158
- Microsoft SharePoint Server 2010: http://technet.microsoft.com/en-us/evalcenter/ee388573.aspx
Such a configuration can be set up by using either a physical machine or a virtualized on: in the second case you'll have several advantages, including the possibility to take snapshots of the configured machine (thus allowing you to revert back to a previous well functioning state in case of a problem) and to clone the machine to set up a training enviroment for SharePoint developers, but this will require either using the trial versions of the mentioned softwares or having multiple license of each of them.
Step 1: Operating System Installation and Configuration
Step 2: SQL Server Installation
Step 3: SharePoint 2010 Server Installation
Step 4: Visual Studio 2010 and Developer Documentation Installation
If you don't have installed Visual Studio 2010 (not Express edition), this is the right moment to do that. After installing Visual Studio, you have to download and install the Microsoft SharePoint 2010 SDK; do not forget to check for the availability of updates for the Visual Studio products and documentation. Now you're ready to develop SharePoint 2010 applications.
See Also
- SharePoint 2010: How to Set Up a Development Environment
- Wiki: Development Portal (en-US)
- Wiki: Platforms Portal (en-US)
NOTE: the following links are external to TechNet Wiki.
Books
- Microsoft SharePoint 2010 Unleashed (Chapter 3: "Installing a Simple SharePoint Server 2010 Farm") by Michael Noel, Colin Spence (SAMS Publishing, 8 October 2010)
- Microsoft SharePoint 2010 Administrator's Companion (Chapter 3: "Optimizing SQL Server for a SharePoint 2010 Implementation", Chapter 4: "Installing SharePoint 2010") by Bill English, Brian Alderman, Mark Ferraz
Other Languages
This article is also available in the following languages:
Italian (it-IT)