TFS acccess rejected error while doing validation using parallels and Visual studio 2013 on Mac

Question

I am running a visual studio with TFS in parallel on a Mac. In parallel, my projects are actually pointing to the Mac docs folder. I can open and edit projects without problems, and also click them on the server.

I recently turned on TFS source control. Whenever I try to do the initial push or checkin, I get a "Path access denied" error message for all individual files.

I really DO NOT want my file to be on a virulent machine, so can someone tell me how to fix permissions to allow TFS to access these files and perform a check? Thanks in advance!

here is an example of the output window when checking ...

V: \ MeYearly \ packages \ Newtonsoft.Json.5.0.6 \ lib \ portable-net45 + wp80 + win8 \ Newtonsoft.Json.xml: access to the path is denied. V: \ MeYearly \ packages \ Newtonsoft.Json.5.0.6 \ Newtonsoft.Json.5.0.6.nupkg: access to the path is denied. V: \ MeYearly \ packages \ Owin.1.0 \ lib \ net40 \ Owin.dll: access to the path is denied. V: \ MeYearly \ packages \ Owin.1.0 \ Owin.1.0.nupkg: access to the path is denied. V: \ MeYearly \ packages \ repositories.config: path access denied. V: \ MeYearly \ packages \ Respond.1.2.0 \ content \ Scripts \ reply.js: path access denied. V: \ MeYearly \ packages \ Respond.1.2.0 \ content \ Scripts \ reply.min.js: access to the path is denied. V: \ MeYearly \ packages \ Respond.1.2.0 \ Respond.1.2.0.nupkg: path access denied. V: \ MeYearly \ packages \ System.Linq.Dynamic.1.0.0 \ lib \ net40 \ System.Linq.Dynamic.dll: access to the path is denied. V: \ MeYearly \ packages \ System.Linq.Dynamic.1.0.0 \ System.Linq.Dynamic.1.0.0.nupkg: access to the path is denied. V: \ MeYearly \ packages \ Twitter.Bootstrap.3.0.1.1 \ readme.txt: path access denied. V: \ MeYearly \ packages \ Twitter.Bootstrap.3.0.1.1 \ Twitter.Bootstrap.3.0.1.1.nupkg: access to the path is denied. V: \ MeYearly \ packages \ WebGrease.1.5.2 \ lib \ WebGrease.dll: path access denied.

Answer 1

I found a workaround for this. I was able to register by postponing the pending changes first.

Answer 2

You need to place files locally on your virtual machine.

Checking and exiting what is valid; remote location is not supported. If you want to have files on your Mac, you can use Team Explorer Everywhere on eclipse and the command line. You will need to switch to your Mac every time you want to check which one sucks ...

Answer 3

Another solution without having to put off :

I did to change the local workspace to the server workspace in Visual Studio (macOS Sierra + Windows 10 on Parallels);

• File> Source Control> Advanced> Workspaces ...
• Select a workspace from the list and click "Edit" ...
• Hit Advanced →
• Change the location to the Server and click OK and Close

You should now be able to register without requiring a delay.

Answer 4

I have a similar question again.

This works well in Parallels. I opened a ticket with Microsoft.

We spent almost three weeks finding the problem - but it seems like the Parallels update, released at the end of 2014, is the culprit.

Since Parallels is not very responsive to consumer complaints, we probably will not be able to get permission at any time in the near future.

Answer 5

You will need to reconfigure the source control. Go to File ---> Source Control -----> Advanced ----> WokrSpace and delete it.