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 for Bug 55608 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
I'm aware that this issue has come up in the past, such as at https://bugzilla.xamarin.com/show_bug.cgi?id=36190. I can therefore only assume this is a regression.
With 15.1 (full version info below), I am frequently running into this problem. Android builds will stall with:
>Could not write lines to file "obj\Debug\Utility.csproj.FileListAbsolute.txt". The process cannot access the file 'C:\Users\Kent\Repository\xxx\Src\Utility\obj\Debug\Utility.csproj.FileListAbsolute.txt' because it is being used by another process. It's not always the same csproj file, though it is normally one of the "base" projects upon which lots of other projects depend.
My interim solution is to cancel the build, exit VS, do a git clean -xdf, then start VS again. Of course, this is incredibly annoying and time-consuming.
Strangely, I also see this warning output when doing iOS builds, but it just doesn't seem to stall the build there.
Full version info:
Microsoft Visual Studio Enterprise 2017
Version 15.1 (26403.7) Release
Microsoft .NET Framework
Installed Version: Enterprise
Visual Basic 2017 00369-60000-00001-AA208
Microsoft Visual Basic 2017
Visual C# 2017 00369-60000-00001-AA208
Microsoft Visual C# 2017
Visual C++ 2017 00369-60000-00001-AA208
Microsoft Visual C++ 2017
Visual F# 4.1 00369-60000-00001-AA208
Microsoft Visual F# 4.1
Add New File 3.5
The fastest and easiest way to add new files to any project - including files that start with a dot
ASP.NET and Web Tools 2017 15.0.30320.0
ASP.NET and Web Tools 2017
ASP.NET Web Frameworks and Tools 2017 5.2.50303.0
For additional information, visit https://www.asp.net/
Azure App Service Tools v3.0.0 15.0.30209.0
Azure App Service Tools v3.0.0
Common Azure Tools 1.9
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
File Icons 2.6
Adds icons for files that are not recognized by Solution Explorer
Hides the Visual Studio main menu, similar to Windows Explorer and Internet Explorer
Integration of the ILSpy Decompiler into Visual Studio.
KofePackagePackage Extension 1.0
KofePackagePackage Visual Studio Extension Detailed Info
Merq 1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package
Mono Debugging for Visual Studio Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.
Continuous Testing Tool for .NET
Copyright © 2010-2016 Remco Software Ltd
NuGet Package Manager 4.1.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
Visual Studio Extension for opening files on GitHub.com
Saves editor formatting settings as part of each solution.
Snippet Designer 1.6.5
Snippet Designer is a Visual Studio plug in which allows you to create and search for snippets inside the IDE
SQL Server Data Tools 15.1.61702.140
Microsoft SQL Server Data Tools
Trailing Whitespace Visualizer 2.5.83
Keeps your code files clean by making it easier than ever to identify and remove any trailing whitespace
TypeScript tools for Visual Studio
Visual Studio Tools for Universal Windows Apps 15.0.26403.07
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.
Color output for build and debug windows - http://mike-ward.net/vscoloroutput
Xamarin 184.108.40.206 (3f99c5a)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK 220.127.116.11 (b16fb82)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 10.8.0.174 (7656cc6)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
## Preliminary cross-referencing note
For recent appearances of symptoms involving *FileListAbsolute.txt, please see recent bug reports that mention FileListAbsolute.txt such as:
- Bug 54966
- Bug 54467
In particular, if you get a chance to try applying the change from Bug 54467, Comment 13, that might be a quick way to check if this is indeed a duplicate of Bug 54467. Thanks!
Here's the information about that change for reference:
Edit the C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Microsoft.Common.Targets\ImportAfter\Xamarin.Common.targets
Edit the C:\Program Files (x86)\MSBuild\14.0\Microsoft.Common.Targets\ImportAfter\Xamarin.Common.targets
(you'll need to be an administrator to edit either one)
Update the `GetBuiltProjectOutputRecursive` Target to contain the following nodes instead of the current ones:
Condition="$(_BuiltProjectOutputs.Contains('%(_MSBuildProjectReferenceExistent.FullPath)')) == 'false'" />
<!-- Add all the top-level projects that will be added by the @(BuiltProjectOutputGroupKeyOutput) further below -->
I'm seeing this building Example.Droid project from the MvvmCross repo located here: https://github.com/MvvmCross/MvvmCross.
I tried the workaround from C1 above and it did not fix my problem.
Sorry I see it when *deploying* that project (you have to go into the solution configuration and enable deploy for that project). It reproduces every time.
I just tried turning Fast Deployment off and now it seems to work.
Correction: Turning off Fast Deployment only worked the first time.
Ok more info:
Turning off Fast Deployment once allowed the build to deploy. The next time it failed to deploy. I then went in and TOGGLED Fast Deployment on and then off again and it deployed again. This is repeatable.
So to sum it up: when I hit this I go into the project settings and toggle Fast Deployment to checked and then to unchecked and it gets me past this issue.