We recently updated our installations to 10.0.16 which has caused a warning that we need to update VS to 2017 on DEV environments by April 2021. On a newly deployed DEV VM I am having difficultly both connecting to DevOps project and maintaining that connection for more than an hour.
When opening VS 2017 on DEV VM it will not automatically connect to DepOps project https://dev.azure.com/XXXXX. I click on connect to server and re-enter credentials and refresh the list and eventually I am able to see the project and connect to it. After an hour or so if I try to do a check out or check in for example I am forced to repeat this process.
My question is has anyone else seen this behavior and what can be done to fix it. I am able to log in to the DevOps project via web browser just fine and I do have permission to check in code on the project.
Weirdly in VS 2015 the server path was https://XXXXX.visualStudio.com which worked flawlessly.
Regards,
Don Shields
