Remember the strange build IO sharing conflict problem with Net Core 2.0 in MacOS 10.13

I believe some friends like to put the project directly on the mobile hard disk to work, in order to facilitate back and forth on multiple computers or different operating system platform on the code brick, the format of the disk is basically exfat (like on MacOS with NTFS or FAT is the big guy), Here we do not discuss the EXFAT format advantages and disadvantages, anyway, he is free, just remember once on the Mac on the strange problem, I hope to have encountered the problem of friends can refer to, as follows:

• Sharing conflicts, what ghosts, first exclude account permissions issues, now who's private computer is not an Administrator account login!
• Is it a file access issue that appears above the exFAT? Also impossible, three platform under the default permissions are all "Everyone"!
• A friend who is not close in the process of file IO Please see clearly that this is the MSBuild symbol library file, unless you manually write custom compilation symbols, you will never be able to modify it, and compile the environment for the code input and output.
• Is Rider ReSharper API a problem on Mac? Sharing conflicts will still occur with the dotnet build command instead!
• Look at the disk tool under the Mac, is normal, no file corruption or bad, consider whether it is a Mac on the exFAT a bug, after all, exFAT is a set of disk format system developed by Microsoft, Apple just did the compatibility function, perhaps this compatibility is not perfect.

With this question, the project is completely copied to hfs+ (i buy karma, 1.14G ...), compiled again, build successfully!

Oh, yes, Linux installs the Exfat-utils tool to mount the EXFAT format disk and does not appear as a "sharing violation" issue.

Remember the strange build IO sharing conflict problem with Net Core 2.0 in MacOS 10.13