VM-based Development Environment · Amr Eldib 

VM-based Development Environment

I love VMs. To have a sandbox inside which there’s an operating system of your choice where you can try anything and not fear its effect on your host machine, that is empowering.

I started using VMs a long time ago, but recently I moved to what I call a “VM-based Development Environment”. As a GIS developer, I have a problem which is that ArcGIS (the main GIS application/platform I’m using) doesn’t allow for side-by-side installation. So, if you want to install version 9.3.1, you have to uninstall version 9.3. And those are two different versions against which you have to develop and test your code.

Over the years, I had a simple solution. Pick a version that I mostly work with and install on my development machine. If I’m moving to a new project that needs a different version, I would uninstall the version I’m using and install the new one. This is, aside from being painful and inefficient, an outdated solution and it created another problem that I found out about at the end of one project I was working on.

Because my personal machine was updated and I install all these kinds of applications with their requirements, there was a software requirement I didn’t add to the installation package and that caused a problem on one client’s machine.

When I started using VMs, I moved the secondary versions of ArcGIS (the ones other than the version I’m mainly using) to VMs. Also, VMs helped with testing, especially when testing installation packages using snapshots (I’ll talk about that later). However, when I faced the missing requirement problem, I decided to take VMs a step further.

I’m using my machine for my personal software (Browser, Outlook, Office, Video, Music, Social Media, etc), and removed all development-related software (including ArcGIS) to a Virtual Machine. So when I work on code, I turn on a VM and start coding on a machine that has the least number of software installed.

Ups

Moving all development work to a VM offer number of advantages:

Tips

Building a VM is not that difficult but if you’re going to create number of VMs, few if not tens, maybe I can help with some tips:

VMClass-OS-InstructionSet-VisualStudioVersion

for example:

Dev-7-x64-10

is a development machine with Windows 7 x64 and Visual Studio 2010

Downs

Using VMs as your main development environment isn’t hassle-free and it does have its own disadvantages:

Two Update Windows, one for a VM and the other for my host machine.

I’ve used VMs for development for quite a while now, and I feel that it improved how I work. Give it a try a let me know if it helped.


Share