Install walk through
For a complete walk through with screen shots from a base Windows server follow these steps here at Install SharePoint 2010 Public Beta on Standalone Windows Server 2008

Environment Requirements

"In any development environment, you should use a computer with an x64-capable CPU, and at least 2 gigabytes (GB) and preferably 4 GB of RAM for SharePoint Foundation, and 6 to 8 GB of RAM for SharePoint Server." Setting Up the Development Environment for SharePoint Server - MSDN

* At least Windows Server 2008 64 bit OR direct onto Windows 7/Vista 64 bit

  • SQL Server 64-bit (2005 or 2008)

General Tuning Recommendations

  • Invest in an SSD drive to maximise disk I/O
  • Invest in 4GB + to ensure there are enough memory resources for your workstation
  • Invest in secondary (external) drive (SSD, ESATA, USB) - you will need it when virtualizing
  • Stop and Go scripts - Emmanuel Bergerat’s post has some nice scripts to run to keep services purring


Physical Machine

Pro Con
Isolated Must be 64-bit Server2008/Win7 workstation (see below)
Developer Control Tied to one instance of SharePoint, this may not be appropriate if you want to isolate your client code bases for conflicts, especially if you are targeting a specific release of SharePoint 2010 e.g. Beta 2, RTM, SP1 etc., or feature set like Foundation, Standard, Enterprise
  Hard to backup
  Will slow your normal every day work down as it’ll always be running regardless of you using it or not

Option 1: Windows Server 2008 R2

Pro Con
  limitations around drivers and software support

Option 2: Windows Vista/Windows 7

Pro Con
Most organisations would have made the move to Vista already and probably planning to move to Windows 7. So this is a good option for those who don’t want to worry about Virtualisation at all. Can’t do User Profile imports and other server related things without other dev/test servers to connect to

Workstation Virtualisation

For a virtualised environment, a minimum of 2GB RAM is required for the guest as well as 50GB HDD space. There has been feedback that you really need 3GB. The guest virtual machines will run more efficiently if you allocate more than one CPU also.

Pro Con
isolated Need high spec’d workstation
clone, pause, snapshot your VM instances  
can migrate these to Rack Virtualisation or between workstations  
developer has full control  

Option 1: Hyper-V

Pro Con
free with Windows Server 2008 R2 your host needs to be Win Server 2008 R2
Very good performance Poor copy/paste experience

Option 2: Boot-VHD

Pro Con
feature comes with Win 7/Win Server 2008 R2 (essentially free) means you’ll be booting in and out of a VMs to do non dev stuff
  Tied to whatever machine it is built on (disk virtualisation) so hard to port to new machine

More on boot-vhd here

Option 3: VMWare Workstation

Pro Con
can be run on laptop/workstation e.g. Vista/Win7 licensed product (not a lot though USD$189)
Unity mode (virtualized the Windows on your main OS - ie no server desktop)  
Teams (group VMs into teams  
Supports DirectX (faster gfx)  
Multiple snapshots  
Support x64 guests on x32 host  

Option 4: VMWare Server

Pro Con
can be run on laptop/workstation e.g. Vista/Win7 Version 2 is web based (Apache Tomcat + JSP) and may be sluggish. Opt for Version 1
free product Single snapshots

Option 5: Sun Virtual Box

Pro Con
can be run on laptop/workstation e.g. Vista/Win 7  

Option 6: VMware ESXi (Can be used in small business server environments)

Pro Con
Bare metal hypervisor (very fast!) Requires dedicated hardware
Free Lacks VMware tools such as VMotion
Large hardware support  
Can move VMs between Server, Workstation and ESX  

Rack Virtualisation

Pro Con
Incredibly fast Will mean having off-workstation hardware to run ESX typically shared with other virtuals

often doesn’t get priority CPU and RAM resources
Can remote debug from workstation Requires access remotely over internet if mobile
Workstations can be lower spec’d Typically not going to get one VM per Developer so not isolated
  Slower provisioning if not administrator of environment

Option 1: Hyper-V

Option 2: VMWare ESX Server

Pro Con
Bare metal hypervisor (very fast) Expensive
Includes VMotion (failover measures) Small hardware support
vSphere allows templates of servers Works best with 2+ servers (inc. management box)


Virtual PC

Can’t use Virtual PC as does not support 64-bit guest and SharePoint 2010 requires this

IE support

Will not support for IE 6

Sample rigs

Dual Virtual Machine setup

This setup will work with whatever virtualization s/w you are using. The idea is to not use the SharePoint 2010 machine as a Domain Controller (which will save you a lot of installation troubleshooting/workarounds). (Tested on a HP EliteBook 6930p with VMWare Workstation 7)

Server #1

This server is a Windows Server 2008 R2 x64 Core installation with 512MB memory, 1 CPU, 1 Core.
Only install Active Directory and run dcpromo, then enable remote administration and enable the AD web services (net start adws). Nothing more should be done.
(Another good thing is that you can reuse this server and prepare the AD with sample users etc)

Server #2

This server is a Windows Server 2008 R2 x64 installation with (at least) 4096 MB, 1 CPU, 1 Core. If possible pump up the memory.
Install SQL Server 2008, SharePoint 2010, Visual Studio 2010, SharePoint Designer 2010, Office 2010. Install the Active Directory Services role, but do not run dcpromo, so you get the AD MMC snap-ins.
Note: Cap your SQL Server so that it uses at most 25% of the total memory, since SQL Server is quite greedy.
As long as you are not enabling all SharePoint Service Application this setup will run smoothly and you will have good dev experience.
Use a lot of snapshots so you can clone it and have multiple versions of this one, that will also save you a lot of time.

External References

The following sub pages will cover all aspects of getting started with WSS 4.0 and SP2010 development.

There are plenty of other resources out there too!

Visio Services will allow the viewing of Visio files in a Web Browser.

  • Real-time visual rendering of Workflow States

External References

Activating the Developer Dashboard

On Demand




Japp Vosser has already extended the dashboard to show a graphical view…as shown above, a CodePlex project is on the way!

External References

Source: Japp Vossers

External References

"Visual Studio 2010 introduces a package designer, which makes viewing and managing packages much easier. If you double-click the Package node, the designer opens. The designer provides the ability for you to add and remove features from your deployable package. This designer represents a significant step forward in helping developers shape their SharePoint solutions through the addition of features." Steve Fox, MSDN

External References

There are various new Event Receiver hook ins available and these are also available to be created in the new Event Receiver Wizard

List Events

A field was added
A field is being added
A field was removed
A field is being removed
A field was updated
A field is being updated
A list is being added
A list is being deleted
A list was added
A list was deleted

List Item Events

An item is being added
An item is being updated
An item is being deleted
An item is being checked in
An item is being checked out
An item is being unchecked out
An attachment is being added to the item
An attachment is being removed from the item
A file is being moved
An item was added
An item was updated
An item was deleted
An item was checked in
An item was checked out
An item was unchecked out
An attachment was added to the item
An attachment was removed from the item
A file was moved
A file was converted
The list received a context event

List Workflow Events

A workflow is starting
A workflow was started
A workflow was postponed
A workflow was completed

List Email Events

The list received an e-mail message

Feature Events

A feature was activated
A feature is deactivating
A feature was installed
A feature is being upgraded

Web Events

A site collection is being deleted
A site is being deleted
A site is being moved
A site is being provisioned
A site collection was deleted
A site was deleted
A site was moved
A site was provisioned

External References

"Also note in the Solution Explorer the presence of the Features and Package nodes. These are new infrastructural parts to Visual Studio 2010 that package a SharePoint solution using a SharePoint feature." Steve Fox, MSDN

External References