CODEWITHSUNDEEP
tfsazure-devopstfvc
eidylon
eidylon

Reputation: 7238

Can't check in changes to TFS

I am having issues trying to check in changes to TFS hosted on Visual Studio Online. Started just last week. I am running Visual Studio Professional 2017 version 15.5.2.

When I try to check in changes, I get this error:

C:\My\Workspace\Path\Project\File.cs: Download of item $/Workspace/Path/Project/file.cs was not completed. Perform a get operation to correct. enter image description here

Okay, whatever. Sounds simple enough. So I go to the problem file and do a Get Latest Version. When I do that, I then get this error: 

Source Control Explorer  
The network path was not found.

enter image description here

The output in the Output window after attempting the get is this: 

Conflict C:\...\...\...\...\...\Program.cs - Unable to perform the get operation because you have a conflicting edit
Automatically resolved conflict: edit: C:\...\...\...\...\...\Program.cs as TakeTheirs
The network path was not found.

I have read a number of posts, and tried a number of things. None have fixed the issue. Things I have tried...

Anyone have any other ideas? The next step I see in my future is having to uninstall and reinstall visual studio, but I'm REALLY trying to avoid that.

Upvotes: 2

Views: 6581

Answers (2)

eidylon
eidylon

Reputation: 7238

By the by, ... I had this issue again today, and had a slightly different fix. When I went to delete my workspace, I found that a prior aborted new project had somehow added additional working folder mappings to my workspace. So I deleted those, after which VS said it needed to restart. So I let it, and now everything seems to be working fine.

Just figured I'd let people know, in case they find that situation, so they needn't go through with the whole other drastic measures, to check this first and try it if it applies.

Upvotes: 0

Andy Li-MSFT
Andy Li-MSFT

Reputation: 30372

So, the solution is Deleteing and recreating the workspace.

You will meet similar issues when a workspace is messed up.

Generally, you can try below item to fix such an issue:

  • Disconnect any instance, close VS, then delete the cache folder located at: e.g. %localappdata%\Microsoft\Team Foundation\7.0\Cache, then restart the VS, connect to TFS/VSTS again.

  • Remap the workspace to a new folder

  • Delete the old workspace and create a new one, map it.

Upvotes: 4

Related Questions