You can set up your RuntimeConfig.xml as desired and not specify a start up project. Then you can specify the startup project on the command line when starting OpenSpan.Runtime.exe. You could then create additional shortcuts on the desktop, one for each solution the user needs to run.
Runtime does not support running multiple deployment packages at the same time, although it is technically possible. As suggested above, if you have more than one package your user's will need throughout the day, then you can create shortcuts to each deployment package by using the command above. If you use OMC, then users will be prompted whenever they start Runtime to choose between any packages that they have been assigned (unless they have only one).
What about the following...? What impact, if any, would they have..? Would these settings work or help if running locally off of a File Server as compared to OMC? If running through OMC, does that limit our options in our ability to possibly run multiple runtimes and load multiple packages..?
Runtime Configuration Settings XML File
SingleCopy – When set to True, only one instance of Runtime can be run on a desktop.
Set to False to enable multiple instances of Runtime to run. The default is True.
CanRunMultiplePackages – Set this key to True if you want Runtime to load all of the packages
assigned in the Deployment Portal. The default is False. If this key
is set to False and multiple packages are assigned in the Deployment Portal,
the user is prompted to specify which package to load.
<!-- If CanRunMultiplePackages is true all packages assigned in OMC will be loaded by Runtime. -->
Only one deployment package can be run at a time. This applies to either OMC or running off of a file share. The SingleCopy key is used for Citrix Mixed Mode and not supported for use elsewhere. I am not sure what the use case for the CanRunMultiplePackages is for, but it is for OMC only anyway and not is not applicable when loading the package from a file share.
Thanks for the response. Well, I was not so much interested in the "file share" configuration as we do utilize OMC, so that is why I was asking about "CanRunMultiplePackages". Given that it states that Runtime would load "ALL" Packages, then the question becomes - Why would one want to do that? If the Runtime has loaded all Packages, then that would seem to imply that you could either run more than 1 at a time or that you could dynamically swap them out without having to re-launch the Runtime and select a specific Package....? I am surprise that there is little to no documentation on the usage of "CanRunMultiplePackages", but I have not been able to find any other than the fact that it resides in the Runtime Config XML file under App Settings.
This is a mode that we have not officially released. Technically, through OMC you can setup a user with a controlling project that starts activities that other projects would respond to. In this case, you could assign multiple projects to a user and they would all load essentially operating off of the same set of activities. You would not be able to use this to run two different projects.
Question: When launching Packages in this manner, what about the Runtime Version? Meaning, I have Package A (7.1.68) and Package B (7.1.75) and the current Users installed Runtime Version is 7.1.75, so can they load and run both Packages without issue? What if the User's Runtime Version was only at 7.1.68, would they still be able to run Package B..? Would seem doubtful, especially if Package B included some fix that was in 7.1.75.
If packages are built and deployed within Studio using different Runtime Version, how can a User actually run each on the same desktop? Either within the context of OMC or standalone (outside) of OMC..?
In order to manage this automatically you need the Updater and OMC (Pega Robotics Automation Deployment Portal) enabled which will allow you to switch the user back and forth. Since settings are user based, however this is not particularly straightforward. The user can not directly switch packages - you will need to switch settings in OMC before they run the package.
If you do not have both of these in place you would need to install/reinstall between running packages. Sometimes you can run a solution with no issues on a higher version of the runtime, but it is not recommended.