Do you know that developers should do all their custom work in their own SharePoint development environment?
Last updated by Brady Stroud [SSW] 7 months ago.See historyThis is to prevent their work affecting other developers. During development, you can expect many of these things to happen:
- IIS resets may need to be done frequently, which stops the SharePoint website working.
- Custom web parts can easily introduce memory leaks which can stop SharePoint working.
- You may be running development SharePoint in debugging mode which would hold the server thread.
- You may be reading event or error logs that are being polluted by other developers simultaneously.
Thus, all SharePoint customization and development must be done on a Virtual Machine. No ifs, no buts.
- It's very important to correctly setup a SharePoint environment for development. Correctly configured, this will save you a lot of trouble later on.
- From time to time, you can seriously screw/damage a SharePoint installation during development and it is best not to install SharePoint on your day-to-day machine.
- Additionally, when you start a new SharePoint project you don't want to carry all the baggage from previous customizations that could potentially affect your new project.
There are many other benefits of using a virtual machine for development
- Virtual machines can be fired up and shut down easily
- Virtual machines can run faster, via being located on a different server and thus it doesn't waste developers' own computer resources
- Virtual machines can be copied and brought to a client for demonstration or testing
- They are the best way to quickly test or experiment with something new
- Virtual machines can frees up resources on the host, so it doesn’t waste resource when developers are not working on SharePoint
- Virtual machines can be easily cloned to scale up the development team
- Virtual machines enable developers to work in Windows Server 2003 / 2008 environment so they will be aware of the configuration issue when deploying to staging and production
There are few considerations when using Virtual Machines:
- Need to activate additional servers
- Need at least 2 GB of RAM for SharePoint 2007
- Need at least 4 GB of RAM for SharePoint 2010
-
Virtual PC does not support 64 bit Operating Systems
- If you’re using Windows 7 or Vista, we recommend using ‘boot to VHD’ or VMWare
If you are after a clean, pre-configured SharePoint server image to test SharePoint, the easiest way is to download a trial VM from Microsoft Tip: More info on setting up SharePoint VM