Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Description of Problem:
compile error: Sharing violation on path
Steps to reproduce the problem:
1. compile source
I get this error:
Error MT2001: Could not link assemblies. Reason: Sharing violation on path /Volumes/APPDEVELOP/Keezen/KeezenIPad/obj/iPhone/AppStorePaid/mtouch-cache/PreBuild/System.Core.dll.mdb (MT2001) (Keezen Complete)
How often does this happen?
This volume is MS-DOS FAT32 formatted
@Will, Could you provide Project for which you are observing this error or could you provide full steps so that I can reproduce this issue at my end?
I am having this problem as well (and my partition is FAT32 as well)
I have a dual boot MacBook Pro (Windows 8/Mavericks) and the code lives on a shared FAT32 partition so I can access it from both OSes.
I moved the project to the Macintosh HD partition (instead of the extFat partition) and the code compiled fine.
I get the same issue as Narayan Sainaney. I create a new solution on a FAT32 drive (which is a secondary drive) and the error is produced 100% of the time.
## Partial workaround
In case it's helpful for anyone hitting this issue, note that you can partially work around the issue by changing the location of the `obj/` folder so that it is written to a non-FAT drive.
For example, for the "Debug|iPhone" configuration, you could open the `.csproj` file in a text editor and add the following line anywhere within the `<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|iPhone' ">` element:
> <IntermediateOutputPath Condition=" '$(OS)' == 'Unix' ">\Users\macuser\IntermediateOutput\iPhoneApp1\obj\iPhone\Debug</IntermediateOutputPath>
(Note: remove the > greater-than character from the beginning of the line.)
You can use this element to change the output path of the `obj/` folder to any HFS+ formatted location you like. After redirecting the `obj/` folder to my user folder (`/Users/macuser/`), I was able to build and run the Xamarin.iOS project stored on a FAT-formatted drive.
The `Condition=" '$(OS)' == 'Unix' "` conditional will ensure that this special `obj/` output path is _not_ used when building via Visual Studio on Windows (see ).
>  http://www.mono-project.com/archived/porting_msbuild_projects_to_xbuild/
Not sure if this is fixable in the BCL, but it's certainly not fixable from Xamarin Studio.
Does this happen only after debugging the app? If so, perhaps the mdb file is still open by either your app (well, the runtime that is running your app in a Simulator?) or by Xamarin Studio if it had to open the mdb file.
Probably worth using lsof to figure out which process has the .mdb file open.
Looks like Jeff needs more info for this one. Changing to NEEDINFO.
Missed freeze deadline for C5SR4, moving to C6.
Moving the milestone to C7.
merging with another FAT FS issue
*** This bug has been marked as a duplicate of bug 12337 ***