Has anyone had success virtualizing multiple command line tools in Windows?
In a previous SU Question I asked how to setup isollated work envrionments. The over all answer was to virtualize the application. I have done just that using Cameyo with moderate success. I have ran into a few issues that I hope that this question will shed light onto.
Note that I am not sold on Cameyo, it just happens to be the only tool I have tried. If there is a better FREE tool out there to use I would be more than happy to try it.
The GUI portions of the virtualized applications work well using Cameyo, but the embedded compilers that were install along with the GUI install cannot be located. I suspect this is because the tools are embedded into the executable and there for not on the system path or even visible on the file system.
Issue 2 (more generic)
I have tried to install multiple apps into the same virtualized application (Cameyo seems to support this) in order to have a single work environment to maintain. It appears that none of the applications are aware of one another. If I were to install each tool in it's own virtualized application I believe it would only increase these issues.
To clear up some of the comments:
- We use several different IDEs (most embedded targets force an IDE on you).
- The IDE's I am attempting to virtualize are all Windows only.
- It is critical that we be able create the same code (generate the same CRC) no matter which developer builds it. This must hold true across time as well.
- If each of developer installs N programs, it runs the risk of installing a wrong version (ie 4.2 instead of 4.1) which may or may not generate the same code. Even if the user installs the correct version, if they are running different flavors of Windows it could still cause issues.
I have seen most of these issues already with an embedded compiler, so to me it's beyond paranoia and a real problem that I need to address.