mapping already exists for devops / tfs when trying to work on project(s) in vs 2022 that is also being worked on in visual studio 2019

Harvey Brofman 21 Reputation points
2022-02-23T15:23:37.693+00:00

Hi,

I have a project that I am trying to work on in vs 2022 that is currently being worked on in visual studio 2019. obviously, I do not want to switch over until I know there will be no issues with the output results. For connection to version control (devops/tfs), it is not allowing the mapping to be shared between the two visual studio's. I am not sure why it wouldn't allow it or what has to be done to have the project available to be worked on in either environment on the same system. Any suggestions? I saw a few other questions on this in the forum, but they seemed to be about migration, not access for both environments on the same system.

thanks
Harvey

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
5,064 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.