Bug 11156 - Unable to build due to lock build outputs
Summary: Unable to build due to lock build outputs
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.0.x
Hardware: PC Windows
: Normal normal
Target Milestone: 1.3.x
Assignee: dean.ellis
Depends on:
Reported: 2013-03-14 10:28 UTC by Jeremy Lew
Modified: 2013-07-15 14:59 UTC (History)
6 users (show)

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 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:

Description Jeremy Lew 2013-03-14 10:28:08 UTC
In evaluating the Xamarin.VisualStudio plugin (limited to iOS projects so far) I have several times been unable to build my project because the build output files were locked by another process. It seems to be either msvsmon.exe or [myproject].vshost.exe that is holding the locks, and the only way to clear them is to 1) Exit VS2012 2) Kill any instances of msvsmon.exe and [myproject].vshost.exe, 3) Restart.
Comment 1 dean.ellis 2013-03-18 06:28:04 UTC
I have been trying to replicate this issue and so far have been unable to do so. Do you have any further information (or a sample project)
Comment 2 Dominique Louis 2013-06-03 16:15:40 UTC
Unable to replicate. No further info was provided.
Comment 3 Mohit Kheterpal 2013-07-15 14:59:28 UTC
Today we are trying to reproduce this issue. But we are not able to reproduce.

As per comment 1 and comment 2 there is no further information.

Hence we are closing this issue. Changing its status to verified.