2 ms·
The VM originated as the physical machine of a previous developer and for a number of reasons is stuck at XP, hence a lot of the reasons it needs to be network
by WorldMaker 7y ago
The VM originated as the physical machine of a previous developer and for a number of reasons is stuck at XP, hence a lot of the reasons it needs to be network isolated at this point.
Also, because it is from an ancient image I don't want to break it because I doubt we could rebuild the ecosystem from scratch, it feels like it is stuck in VirtualBox, which is I think a large part of the slowdown because VirtualBox doesn't just directly support Hyper-V-based acceleration like just about everyone else finally does. I really need to convert it directly to a Hyper-V VM, but I don't have the free hard-drive space at the moment to have multiple VM copies around, haven't had the budget time, and I'm not sure I trust some of the available tools.
I'm using the last build of Git for Windows I was able to get to install on XP, and I pray that there isn't a compatibility break as right now a shared worktree-less folder as "remote" to the VM internal repo is the only way I'm getting code in/out of the VM. I'm generally happy with VS Code outside of the VM for full text search, but VS Code can't build "Find All References" and "Go To/Peek Definition" maps, and that's the biggest itch that I miss, and VB6 IDE never had a good "Find All References" because it predates that tool in VS by like half a decade at least, and more than a decade before "Peek" sub-editors came about.