Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have been using VMWare as my primary development environment for a couple of years now.</p> <p><strong>Some Environments I typically switch between</strong></p> <ul> <li>Windows Forms / WPF Development (XP, .Net 3.5)</li> <li>Ruby Development - did one website in ruby (XP, Instant Rails)</li> <li>ASP.net 3.5 - for playing with new stuff (XP, .net 3.5, IIS, SQL Server)</li> <li>ASP.net 2.0 - sometime places are still stuck on 2.0 (XP, .net 2.0, IIS, SQL Server 2005)</li> </ul> <p><strong>Some things I have learned</strong></p> <ul> <li>Use XP not Vista. When you are running multiple vms, the extra fluff is really noticeable</li> <li>Give each VM around 1gb (sometimes as little as 512MB). You want to give them the least possible that prevents swapping for what you regularly do.</li> <li>Keep a snapshot of the base install for your stack, before doing any development.</li> <li>Quad Core + 8gb ram is cheap now. I typically have several vms running while developing. If you have less ram or cores, keep the number of running vms down.</li> <li>Turn off software mouse cursors and run in full screen mode (most people don't realize it's a vm until I show them).</li> </ul> <p><strong>Benifits</strong></p> <ul> <li>I can be up in running in any of my major stack in 5 minutes on any pc I own.</li> <li>I can move my entire development environment onto a laptop or another pc in a pinch.</li> <li>I can keep separate dev stacks around easily that can otherwise step on eachothers toes.</li> </ul> <p><strong>Hard Drives</strong>: Your first bottleneck is going to be RAM, but RAM is cheap now so there is no reason not to have 8-16gb. Your next major bottleneck is hard drives in a major way. I now try to have one hard disk per active virtual machine (used in a desktop workload, not server stuff). Raid setups can help tremendously and <strong>SSD's</strong> completely solve the problem if you can afford it. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload