Share via

VS2017 Get latest always give me “A non version controlled file or writable file by the same name already exists locally”

  • Article

Question

Thursday, February 14, 2019 12:06 PM

Thanks in advance. Visual Studio 2017, Windows 10.

Doing a get latest always brings up: "A non version controlled file or writable file by the same name already exists.".

We don't have gated check-ins for any builds. Each time I do a get I have to always select "Overwrite Local File or Folder". I've even deleted the top level folder on my file system and did a brand new get (Advanced | Get Specific Version | checked both check boxes), of everything, and yet anytime a file changes I am prompted with the same dialog.

I've checked Tools | Options to see if there's a get writable setting but I haven't found one.

The files on the file system are not read only and this happens on both my local machine and on the build server (WinServer 2012, VS 2017).

This is very problematic. Does anyone know how I can get past this?

Thanks.

LT

All replies (1)

Friday, February 15, 2019 6:29 AM

Hi,

Welcome to MSDN forum.

Please have a look at the case and hope that will be helpful:

https://stackoverflow.com/questions/40100149/tfs-2015-vnext-build-fails-with-error-unable-to-perform-the-get-operation-becaus

Since our forum is discussing Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor. it is recommend investigating this further with TFS tag on Stack Overflow. Thank you for your understanding.

Best regards,

Joyce

Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].