How to I install multiple versions (of Simulator) on Win10 on same PC? Can it be done?
I have tried installing a later version, but the later version seem to remove all previous version, even if I specify a different install folder path (on C:).
For example, I am using Simulator 2017-3184 (Win10) for stable build of app (only for Win and Android app). And I want to test same app using latest Simulator 2018-3258 (Win10) or I want to try new API using latest Simulator 2018-3258 (Win10) … without removing my current stable version (Simulator 2017-3184, Win10).
If there is any docs which I have missed, please help to advise.
Your other choice is to find a Windows centric solution (versus asking for Corona specific help.)
Googling “windows 10 install multiple versions of same app” turns up some possibilities, but honestly I don’t think you’ll like the end results and risks you run trying to do this.
There are multiple apps (only Windows and Android), all of them have been built and tested on a stable version (Simulator/Win10). In fact, I have probably coded some work-around earlier in order to ensure this.
Those app that would benefit from the later version, with new API, will be first candidate to go on newer version (Simulator/Win10), for testing and etc. The rest of the app would remain on stable version first. App which require new features but not the new API, stay on stable version. App which require code enhancement but not the new API, stay on stable version.
Therefore, the move, if ever to the later version (to become the stable version) would be in phases. Hence, the need to have two build environment, one stable and one later (Simulator/Win10). That is why un-install and install Simulator version is not the first solution I would look at.
I thought that just having like two or more different install folder path, for example,
C:\Program File (x86)\Corona Lab\Corona3184\
C:\Program File (x86)\Corona Lab\Corona3258\
each with their own Simulator binaries, DLL, jars and etc, would do the trick. I just need to make sure I know which version I am launching.
It looks feasible to me. I may be wrong, it seems quite straight forward for Corona Lab to implement.
There are additional complications, such as registry entries, custom installers, etc. that make it considerably more difficult to have multiple versions of the same app on a Windows machine.
Exactly as Rob says. Not everything from a Windows install of an app lives in the folder it’s primary content is installed in.
Before you experiment, backup your computer. It will probably be fine, but it would be a real shame to lose your data or settings over experiments like this.
Another possibility that I’m not sure will work is to create guest accounts on your PC with different versions of Corona installed.
Share common apps you need between all users, but install specific corona versions for guests 1,2,3…
I hate to say this, but your best option in this case is to test on a Mac.
Worst case, you can use a Virtual Machine to install OS X and then run any number of versions of Corona on the virtual Mac on your PC.
(While I have an actual Macbook Pro, I hate Mac keyboards, key-shortcuts, file system weirdness, and OS X in general, so I only use it for final builds.)
Instead I use a virtual Mac for daily work and tests if needed:
Many thanks to everyone for your response, advice and suggestions. I suppose I would need to explore them, now that what I ask for (and hope for) is not available.
Certainly, there are many other higher priority features, enhancement requests, bug fixes and etc that the community needs (than this). I would consider this matter (and this thread) close, for now.
Once again, many thanks!
Regards, Luan
PS> If need be, in the future, I may post a request for this on http://feedback.coronalabs.com/, for the community to vote on.
This is not something Corona can control. It is a Windows limitation.
Back in the good old days (before most of the readers here were even born) Windows installed everything for an app in a folder and that was it.
You could delete the app by deleting the folder.
You could also have multiple variants of the same program simply by adding new folders with new copies.
It does not work that way in Modern Windows.
Additionally, Corona most likely cannot be built that way any longer. It simply has too many dependencies and requirements that link it to the registry and other parts of Windows.
Your other choice is to find a Windows centric solution (versus asking for Corona specific help.)
Googling “windows 10 install multiple versions of same app” turns up some possibilities, but honestly I don’t think you’ll like the end results and risks you run trying to do this.
There are multiple apps (only Windows and Android), all of them have been built and tested on a stable version (Simulator/Win10). In fact, I have probably coded some work-around earlier in order to ensure this.
Those app that would benefit from the later version, with new API, will be first candidate to go on newer version (Simulator/Win10), for testing and etc. The rest of the app would remain on stable version first. App which require new features but not the new API, stay on stable version. App which require code enhancement but not the new API, stay on stable version.
Therefore, the move, if ever to the later version (to become the stable version) would be in phases. Hence, the need to have two build environment, one stable and one later (Simulator/Win10). That is why un-install and install Simulator version is not the first solution I would look at.
I thought that just having like two or more different install folder path, for example,
C:\Program File (x86)\Corona Lab\Corona3184\
C:\Program File (x86)\Corona Lab\Corona3258\
each with their own Simulator binaries, DLL, jars and etc, would do the trick. I just need to make sure I know which version I am launching.
It looks feasible to me. I may be wrong, it seems quite straight forward for Corona Lab to implement.
There are additional complications, such as registry entries, custom installers, etc. that make it considerably more difficult to have multiple versions of the same app on a Windows machine.
Exactly as Rob says. Not everything from a Windows install of an app lives in the folder it’s primary content is installed in.
Before you experiment, backup your computer. It will probably be fine, but it would be a real shame to lose your data or settings over experiments like this.
Another possibility that I’m not sure will work is to create guest accounts on your PC with different versions of Corona installed.
Share common apps you need between all users, but install specific corona versions for guests 1,2,3…
I hate to say this, but your best option in this case is to test on a Mac.
Worst case, you can use a Virtual Machine to install OS X and then run any number of versions of Corona on the virtual Mac on your PC.
(While I have an actual Macbook Pro, I hate Mac keyboards, key-shortcuts, file system weirdness, and OS X in general, so I only use it for final builds.)
Instead I use a virtual Mac for daily work and tests if needed:
Many thanks to everyone for your response, advice and suggestions. I suppose I would need to explore them, now that what I ask for (and hope for) is not available.
Certainly, there are many other higher priority features, enhancement requests, bug fixes and etc that the community needs (than this). I would consider this matter (and this thread) close, for now.
Once again, many thanks!
Regards, Luan
PS> If need be, in the future, I may post a request for this on http://feedback.coronalabs.com/, for the community to vote on.
This is not something Corona can control. It is a Windows limitation.
Back in the good old days (before most of the readers here were even born) Windows installed everything for an app in a folder and that was it.
You could delete the app by deleting the folder.
You could also have multiple variants of the same program simply by adding new folders with new copies.
It does not work that way in Modern Windows.
Additionally, Corona most likely cannot be built that way any longer. It simply has too many dependencies and requirements that link it to the registry and other parts of Windows.
