Bug 13494 - not able to compile (sharing problem) after automatic update to last version
Summary: not able to compile (sharing problem) after automatic update to last version
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.10
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-26 03:37 UTC by Wil Laan
Modified: 2016-10-18 17:05 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED NORESPONSE

Description Wil Laan 2013-07-26 03:37:45 UTC
Description of Problem:


Steps to reproduce the problem:
1. got update 4.0.10
2. Compiled


Actual Results:
Error MT2001: Could not link assemblies. Reason: Sharing violation on path /Volumes/APPDEVELOP/Keezen/KeezenTrial/obj/iPhone/AppStoreTrial/mtouch-cache/PreBuild/System.Core.dll.mdb (MT2001)

Expected Results:
error free up to prior version

How often does this happen? 
always

Additional Information:

tried to remove System.Core.dll.mdb and shared the folder and compiled again: no luck
Comment 1 Jeffrey Stedfast 2013-07-26 12:02:23 UTC
Some other process has a lock on that file. Perhaps try rebooting? I don't know what else to suggest :\
Comment 2 iain 2016-10-18 17:04:37 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks
Comment 3 iain 2016-10-18 17:05:13 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks