The downside of using a physical device, is that my app needs to talk to an API that is hosted on a test environment with a non-public DNS name. So, for Android testing and debugging, I appear to be stuck with either using a physical device (which was quite easy to get up and running from my VM), or, run the emulator on my physical machine, outside my VM. VirtualBox 6.1 is supposed to support nested hypervisors, but I don’t think it’s quite there yet. Despite reading good things about Hyper-V allowing nested hypervisors, Hyper-V inside Hyper-V just doesn’t perform well enough to be useful. Unfortunately Android emulators don’t work all that well inside a virtual guest. I use VirtualBox to host my guest machines – I’ve tried Microsoft Hyper-V, but for whatever reason it just lacks the performance and flexibility that I’ve found with VirtualBox. I can replace my physical device without going through the pain of rebuilding my development environment, and.one for API dev, one for Mobile dev etc.) I can set up different machines for different workflows (e.g.I can backup and/or snapshot machines so can recover quickly in the event of some failure or error.
The environment is portable, so I can move it between machines.I like to develop inside a Virtual Machine.
0 kommentar(er)
