tag:support.appharbor.com,2010-11-23:/discussions/problems/6213-nugetexe-locked-being-used-by-another-processAppHarbor: Discussion 2018-10-19T03:06:48Ztag:support.appharbor.com,2010-11-23:Comment/185237292012-09-05T15:37:10Z2012-09-05T15:37:10ZNuGet.exe locked - being used by another process<div><p>Are you sure the NuGet.exe in the repository is also the latest
version?</p></div>tttag:support.appharbor.com,2010-11-23:Comment/185237292012-09-09T09:48:17Z2012-09-09T09:48:17ZNuGet.exe locked - being used by another process<div><p>Well,<br>
I used this error as an opportunity to upgrade our solution to
VS2012 and .NET 4.5.<br>
All is new now, including Nuget Package Manager and all nuget
packages.<br>
But right now i'm getting this weird inconsistent behavior - When
i'm getting this nuget "file is used by another process" error, I'm
just committing the app again (by "Test Hook") in github and it
works...</p>
<p>attached an image of 3 uploads of the same commit - the first 2
failed and the 3rd worked...<br>
so right now i'm just committing over and over again until it works
sometime..</p></div>ferdttag:support.appharbor.com,2010-11-23:Comment/185237292012-09-10T14:42:41Z2012-09-10T14:42:41ZNuGet.exe locked - being used by another process<div><p>Inside your repository, there's a NuGet.exe located in a .nuget
directory. This isn't updated automatically as far as I know, so
you'll need to make sure this is the latest version as well. We use
"/m" as a switch to MSBuild to utilize multiple cores and this
fails with older versions of NuGet. The reason some builds succeed
is likely that we're processing another build at the same time
causing MSBuild to only use a single core.</p></div>tttag:support.appharbor.com,2010-11-23:Comment/185237292012-09-12T10:14:22Z2012-09-12T10:14:22ZNuGet.exe locked - being used by another process<div><p>well, I've double and triple checked, and the NuGet.exe file is
the most recent.<br>
(image attached) and i'm still suffering from locked file error</p></div>ferdttag:support.appharbor.com,2010-11-23:Comment/185237292012-09-12T12:43:04Z2012-09-12T12:43:04ZNuGet.exe locked - being used by another process<div><p>Could you add <a href=
"mailto:support@appharbor.com">support@appharbor.com</a> as
collaborator?</p></div>tttag:support.appharbor.com,2010-11-23:Comment/185237292012-09-12T12:45:27Z2012-09-12T12:45:27ZNuGet.exe locked - being used by another process<div><p>you got it</p></div>ferdttag:support.appharbor.com,2010-11-23:Comment/185237292012-09-13T03:45:55Z2012-09-13T03:45:55ZNuGet.exe locked - being used by another process<div><p>This is definitely interesting. Could we get you to try and
remove the NuGet package restore related functionality (details
<a href=
"http://blog.appharbor.com/2012/05/29/upgrade-to-nuget-1-8-to-speed-up-builds">
here</a>) and re-add NuGet package restore. This is to make sure
that your nuget targets file is pointing at the correct
executable.</p>
<p>Michael</p></div>friismtag:support.appharbor.com,2010-11-23:Comment/185237292012-09-14T14:43:26Z2012-09-14T14:43:26ZNuGet.exe locked - being used by another process<div><p>seems like it worked.<br>
thanks a lot!</p></div>ferdt