This post originated from an RSS feed registered with .NET Buzz
by Brad Wilson.
Original Post: It Was Bound to Happen
Feed Title: The .NET Guy
Feed URL: /error.aspx?aspxerrorpath=/dotnetguy/Rss.aspx
Feed Description: A personal blog about technology in general, .NET in specific, and when all else fails, the real world.
I knew this would happen sooner or later. I bought a piece of software that doesn't run on Windows Server 2003. So now I'm wondering what my next step is:
1. Wait for the software to come out with W2K3 patches, if ever?
2. Pave W2K3, put on XP (supported), and run dev in a VMware VM?
There's something appealing about solution #2. It means my dev environment gets to stay clean, because nothing but dev stuff ever gets in there. In theory, no more paving. In practice, periodically saving off the VM files is a very simple backup and restore procedure.
However, I've never tried to dev full time in a VMware VM. I did do some dev work in a Linux VM, but it wasn't quite full time, and the differences between the way the two OSes work is pretty significant. It'll probably take some getting used to. The box is plenty beefy enough (P4 2.53GHz, 1GB of DDR-333), so I guess I'll give it a try with the current OS as the host, and see if it works out okay.
Can anybody share any experience of doing full time dev in a VMware VM?
Previous Topic
