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 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.
Created attachment 5945 [details]
Full Build Output
When attempting to build the attached test project, the following error occurs in the (attached) build log:
error MSB4018: System.UnauthorizedAccessException: Access to the path 'C:\src\XXX\dev\addons\trunk\src\Butler.Tablet.AndroidUi\obj\Debug\res\layout\buildingslistfragment.xml.bk' is denied.
The bk files are appearing somewhat randomly. The user only has axml files in the layout resources folder.
If the user removes the obj folder from source directory, sometimes the build finishes successfully.
Changing build configuration (and thereby build folder), will result in 1 successful build. But afterwards the problem reoccurs. In addition,continuously pressing start debug (f5) will eventually result in success, although it will fail multiple times.
Has attempted to run VS as an Admin with the same results.
Microsoft Visual Studio Ultimate 2012
Version 11.0.61030.00 Update 4
Microsoft .NET Framework
Xamarin.Android 4.10.01073 (d23a19bf)
Visual Studio plugin to enable development for Xamarin.Android.
I am unable to replicate this issue. I suspect what ever permissions are on that temp file are being removed when the file is uncompressed.
Next time if happens can you try going into Powershell and running
Get-ChildItem | Get-Acl
To get a list of the permissions for the the files in the directory that is causing an issue. We might be able to track down where permission is blocking the file from use.
I'm closing this as no further information has been provided and we cannot reproduce similar issues with latest stable builds. Please feel free to reopen if the problem recurs.