Strange Visual Studio TFS behavior when working with share / unc path for Mac

Question

I am working on a Mac with Yosemite. Yesterday I installed Update 4 from Visual Studio 2013 and noticed strange behavior when working with TFS 2013 (and TFS as SCM). My source files are mapped to a UNC loop on my Mac as a local workspace.

When I make changes to my files and try to register, I get the following message:

\\psf\Home\Documents\My\TFS\Customerproject\Source\Calculation\WeightCalculation.cs: Access to the path is denied. 

When I postpone my changes and delete them, I can register the file. I can reproduce this in every file when I get the message "access denied".

Update I just played a little with him: I do not need to parse the files. This is enough to set them aside and check "save pending changes locally." After that I can register.

I tried to remove the read-only flag on Windows, and I made "chmod -R 777 Source" in the source folder to allow access for everyone, but this does not solve the problem. Only bypass mode works.

Running Visual Studio as an administrator also does not solve the problem.

Has anyone else noticed this behavior or have an idea how to solve it?

Answer 1

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 in 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.

---

Note that there are some , but in my case it works fine with the server workspace;

Why should I use a local workspace?

When using a local workspace, you get the following benefits:

Easy to work offline. You can quickly start editing a file when the network connection is unavailable or unreliable. From the Explorer solution you can add, edit, delete, rename, cancel and compare items in your workspace, even if you are not connected to your Team Foundation Server.

It is easy to recover files that you deleted locally. To recover locally deleted files, just get your files.

Visual Studio automatically detects changes. When you add or delete files outside of Visual Studio, the program automatically detects these changes.

Important: One of the drawbacks of using the local workspace is that performance degrades as the number of items increases. See the next section for details.

When do I need to use the server workspace?

When you use the server workspace, Visual Studio saves only one copy of each file. This can significantly reduce disk usage and improve when you have a lot of items. We recommend using a server if:

Your workspace contains over 100,000 items.

You want to use Visual Studio 2010 or earlier to work with the workspace.

You need to use the Enable latest version option at checkout .

Work offline with difficulty and low productivity. . When you are offline in the server workspace, you cannot work with your local files because they are read-only until you check them. You can check files only from Solution Explorer, and only after you switch to offline mode (as described below). While you are offline, you cannot perform any other operations, such as adding, deleting, renaming or canceling.

Tip. . You can improve responsiveness by enabling asynchronous validation. For more information, see the "Managing a Collective Project Collection" section of the settings for your team.