Software is never perfect. Providing the ability to install multiple versions of ArcGIS Pro side by side would allow users to test new versions without having to completely uninstall and reinstall each new version.
Impressed that @SimonSchütte_ct 's workaround for this (frankly rather significant) problem works. It's frustrating that Python versions are apparently the issue here- one would think that this could be addressed by installing per-ArcGIS Pro major version Python directories.
A workaround I have found is to use the 'Sandboxie' program (Sandboxie Classic works, Sandboxie Plus may make it easier to manage). Without ArcGIS Pro installed (having had it installed previously shouldn't be an issue), you set up a new sandbox, install the version ArcGIS Pro you need, required patches, and any required plugins from external vendors into that (this can be done by running the .msi's and .msp's with 'msiexec' from the Sandboxie interface). After this is done you could either install the latest version in its own sandbox, or, just straight on into the normal Windows machine.
The primary advantage to doing things this way, over running ArcGIS Pro in a VM is that GPU access will be conducted directly as with running it 'raw', rather than a GPU being emulated (slow) or having to have expensive cloud costs or do GPU passthrough with the attached virtual desktop infrastructure, server GPUs and Nvidia GRID licensing etc. Disadvantages are that if one needs to install these versions onto multiple machines throughout an enterprise, it's going to be more difficult than just serving up a virtual desktop or virtual application that's installed in one place (though it should be possible with the appropriate use of the command line tools), and that Sandboxie is, effectively, security software, and like other security software may have incompatibilities with other security software installed on your system (though I've noticed no issues with Microsoft Defender).
This would be incredibly useful for our organization as well for all the reasons already listed here. We work with vendors who still need Pro projects delivered in v2.9. We also have run into the Enterprise/Pro versioning issues.
It seems like every version of Pro has a distinct show stopper bug for me at the moment. Due to the inefficient way of migrating between versions, people appear to stop with a least-evil version and wait it out until there is a new feature they cannot live without.
Please provide Pro as a containerised / packaged version so that multiple versions can be available to a user.
Look at the Linux Flatpack / Snap / etc model for inspiration. (Not saying they're perfect LOL)
I understand the limitations and caveats of having different versions but, in my case it will allow me to do my editing in 3.2 (which was fine for that for me) and do the layouts in 3.3.
This will supersede other ideas that revolve around pinning versions, making installing an older version easier, etc. as I've now come to the conclusion that, to be productive, we need a couple of versions running side by side.
I don't want to dive into the high-performant gpu accelerated VM world to achieve the same.... For one person...
@RTPL_AU Looks like that idea was rolled up into this one.
Bumping this thread - we're experiencing version incompatibility issues that are complicating our troubleshooting process. We're having to install various versions of Pro on server machines that don't currently have the software, since our other systems have already been upgraded to newer versions.
@MarkGo I'm right there with you on the server installations. I have 2 vendors that cannot keep up with esri's update cadence so have to continue to run a Pro 2.9 and Map 10.8 instance to work with their tools.
we used to do that with autodesk but uninstall/install and underlying windows os updates made it a mess with things like shared dlls, registry cleanup, etc.
even having esri and autodesk on the same box has had similar problems
now if we are talking about including ArcGIS Pro on a unix os...
we easily had multiple arc/info versions installed on the same workstation by simply copying the program from dvd to a separate folder on disk and edit a .profile file or two
have not fooled with the Pro on a Mac options, boot camp, split boots, virtual desktops, etc.
