While randomly looking through the incoming searches on my blog, I came across a post from Bamboo Solutions - How to install Windows SharePoint Services 3.0 SP1 on Vista. Hacking the installer to allow SharePoint development without building a VM is something I’ve had sitting on my list of stuff to try out for about six months, so it’s good to see someone has put the solution out there.


Removing the VM requirement is a fairly important part of making SharePoint development easier. Visual Studio is really painful to use if you have to go through remote desktop, and even running locally with Virtual PC has its little issues like not being able to bring up intellisense with alt-right.


Being able to install SharePoint locally is certainly a step in the right direction. I’ve had all sorts of issues with things like virtual machines not being approved to connect to the network and therefore being unable to use source control or backup properly. Of course, in that sort of environment Vista probably isn’t SOE either, but it could make things easier.


However, it’s not a perfect solution, mainly in how easy it is to completely screw up a SharePoint installation. Despite the issues with performance and running visual studio, a virtual environment does have a big advantage in being easy to restore to a previous state.


When I’m next working on SharePoint development tools (which may be a while with all the other projects I’m working on at the moment), I’ll probably go with a hybrid approach - SharePoint running on a VM and Visual Studio running natively. I have done this before in a limited way, setting up a web service that deploys an uploaded WSP file and calling it from a piece of the WSPBuilder add-in that hasn’t made it into the official codebase as yet. The main piece of work left to make that system really workable is setting up the remote debugger.


More recently I have been thinking of another approach that may work better - setting up a continuous integration server alongside SharePoint. It shouldn’t be too hard to make WSPBuilder run as part of the build script, and may actually make a shared development server workable.