We are especially interested in the “CanRunMultiplePackages” setting and if that would work for our Desktop Automations…?
We are trying to address a scenario to where we have users that need to run both “AgileDesktop_A” and “AgileDesktop_B” if that makes sense and therefore, instead of having to exist and close the Agile Desktop and reload again with different Package, we are hoping to be able to load multiple Packages and then switch or select within the Agile Desktop which Package the User needs to interact with at any given time without having to exit & re-launch Openspan. Is that even possible….? If multiple Packages are able to load, then how would one switch between them..?
It'd be a good idea to set allow with no package to true and then right click on the Runtime icon. You can load and unload projects from there; I don't think you'll need the can run multiple packages option in that scenario. Give it a try.
Posted: 5 years ago
Posted: 23 Jun 2017 11:09 EDT
Mitchell Vega (Mitchell)
Software Engineer, Robotics Engine
I've taken some time to research your question. The CanRunMultiplePackages property in the RuntimeConfig is for OMC. I'm not sure if your company utilizes OMC but it is an extension of our product that offers cloud-based service to deploy packages to users. This setting only works with OMC. It allows for multiple packages as it implies by starting multiple Runtime processes for the user and loading all the packages that are assigned to the user in OMC. We generally don't recommend using it because it can conflict with your automations if not done carefully.
The setting doesn't allow for dynamic switching of packages as both projects will execute as they're loaded. I have not personally experienced another customer use this setting so I can't attest what it might be used for - I believe it's more of a legacy setting that exists still. Since multiple projects can be added to a single solution, generally, everything can be done in a single package.
If you are finding users needing to switch projects throughout the day, I've found that creating an icon on the desktop with a shortcut pointing to the directory with the solution path as an argument can make it easier for users to switch packages easily: "...\OpenSpan.Runtime.exe" -project="C:\dir1\dir2\solution1.openspan"