I get this message from time to time. I will go into my Source Control Explorer to 'Get' the latest version of a project I haven't worked on in a while. There it shows that the 'Local Path' is 'Not Mapped' even though I know I have mapped it previously. 'No big deal though I will just remap it'. But when I go to map it, it errors saying a mapping already exists.
So deleting the workspace entry from the Edit Workspace dialog and remapping the location indeed resolves the problem. But what is frustrating to me is why this is a problem in the first place. If the location is already mapped (Which it is) then why doesn't the VS client recognize it.
When I go to remove the mapping, everything looks correct, just the way I want it. So why do I have to remap at all. Am I the only one that runs into this issue repeatedly where my mapping exists, but VS doesn't recognize it?