When a demo environment is provisioned in LCS it is always named demo-1 (or sometimes demo-0)
However visual studio workspaces work with the computer name, so if we create a second demo environment (aimed at a different prospect for example), TFS integration becomes a problem.
Visual studio will think that a workspace already exists on the new computer, mapped to the same J:\aosservice\PackagesLocaldirectory.
The only solution is to manually rename the computer, update the web.config, update the visual studio plugin config, reconfigure SSRS, reconfigure SQL, etc which is frankly, a hassle.
My suggestion is to give the computer a random name during the provisioning process instead of always demo-1.
Comments
In deployment settings, at 'Customize virtual machine names' step, you have the option: 'Specify a name for the aos virtual machine' followed by the start index.
Those will allow you to specify a different name than demo and/or change the number.
Blank value and 1 will give you 'demo-1'. 'DevBox' 5 will give you 'DevBox-5'.
Category: Development
Administrator on 5/25/2019 7:40:54 PM
Specify the name of the environment in the Advanced settings tab. We are currently not planning changes in this area.