![]() Why not replicate it when you develop? Also, when I'm not developing (remember this is also my home machine), do I really need to have all of those database services running? Yes, I could turn them on and off manually, but its so much easier to switch a VM on. In a production environment your app is probably not running on the same box as the db. When I develop, I have one VM running my database servers (SQL2000/2005/2008). NET 3.5 sp1? What happens if he doesn't have XXX component? etc? ![]() This approach also makes it easy to play with different software scenarios (what happens if the user installing the program doesn't have. I found plenty of little bugs this way, that definitely would have made it into the wild had I not used this approach. lots of RAM, little RAM, 1 core, 2 core, etc). I also play with the VM hardware settings (e.g. If 32 and 64 bit flavors are available, I also build one of each. When I test, particularly a desktop app, I typically create multiple VMs, one for each platform that my software should run on (Windows 2000/XP/Vista etc). My case is probably extreme though, but here is my logic for doing so. I just built a real beefy machine at home so that I could run multiple VMs at once.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |