I am assuming you have a ServerPC (something like Windows Server 2016) that has Terminal Services setup so that multiple users can login on separate UserAccounts at same time.
If so the solution is:
- Install AwareIM in the normal way to c:\AwareIM
- Install AwareIM Configurator (it is a separate install) to c:\AwareIM_01 ... a separate folder for each user.
- Setup a shortcut on each user Desktop to point at their install of the Configurator.
- Each user (because they have a separate folder) will have their own Configurator Settings ... perfect.
- There is not need to make any settings changes ... all will point ok at the localhost ControlPanel.
We do note that access to the debug output, when such is needed, is most readily done from the ControlPanel.
NOTE: This does not make the development environment any the more multi-user. That is two developers cannot work on the SAME BusinessSpace. Plan that each developer use (work from) their own project (Business Space/BSV). Keep one of the BusinessSpaces as the master and merge the works of others into that.
We find the merging works pretty well. A BusinessObject can be deleted in the master and another (of the same name) copied from another project and it will maintain the referential links and shortcuts etc etc. We do note that the UpdateRules and DeleteRules do NOT get copied when you do this ... those have to be copied separately ... this is a bug in my book.
If you plan to "pass" development of a BusinessSpace from one developer to another it is best (safest) to have both the developers close their Configurators and then re-open. This to ensure that the work is saved and (subsequently) that goodie version is loaded into the new developers Configurator.
Be sure to Export the BSV of both source and target before doing a merge. We name ours like below so that they stay in a sorted order:
BusinessSpaceName_20180718@0930.bsv
The ones that are Published get named with the version like: BusinessSpaceName_20180718@0930-v2.65.bsv
