If you setup multiple environments on the same machine, you'll run into the issue that a config file that holds the connection to the repository, is stored in the App_Data folder of the user running the service and can have only 1 version.
So 2 environments on the same machine need 2 services, run by different service accounts. With that we can run into trouble with customers who don't have accounts for each environment
If that's so, wouldn't it be better to make the config file environment-based instead of user-based? As it is setup now we cannot use 1 serviceaccount to run both environments on the same machine, because of that file.
I think that it's more logical that you can choose the repository in the Environment Properties screen, so it becomes user-independent:
Is this something to consider for a future release?
