-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"GenerateDepsFile" task failed unexpectedly. The process cannot access the file *.deps.json #2076
Comments
Just a quick update on this for anyone listening: Following this comment #739 (comment), I was able to unblock MS Build by disabling multi-proc builds with adding the switch This MS Build bug is even more crazy because MSDN docs say:
... but it doesn't seem like it. π |
Is there a reason you're not building the .sln directly, and are instead building each project individually? The TeamCity command line includes
Are you setting that as part of your build customization, or is TeamCity doing it automatically? Setting
The first one is net40; the second is netstandard2.0. It'd overwrite with the 1.3 version too, but the build failed before it tried. Aside: multiproc
There's a |
Hey @rainersigwald , Thanks so much for your help. I've been in the weeds with this issue so much I lost the forest for the trees. I didn't realize setting I guess the main thing that mislead me into this trap was the following F# FAKE
Originally, I had an Everything is building successfully without errors. π Thank you again for your help! β‘ π "I was struck by lighting. Walkin' down the street..." |
* Patch WebApiProjects with a Condition on Import This allows the dotnet remove/add commands to work without trying to import a non-existent project * Follow project references when updating import conditions * Undo unnecessary change * Specify solution file explicitly in build This might help the random build errors, according to dotnet/sdk#2076
β¦119.2 (#2076) [main] Update dependencies from dotnet/arcade
In my situation, the reason for the problem was, that there has been different LangVersion settings within the several project files. |
Hello.
I've been stuck on a really bad MS Build error for a few days now. Kinda at a loss as to why MS Build is having a hard time building my projects. My issue seems eerily similar to #545 and #739. Google isn't any help either. ποΈ
I have a SLN file that contains:
Bogus.Healthcare
.NET Core Assembly project. Multi-targeting:<TargetFrameworks>net40;netstandard1.3;netstandard2.0</TargetFrameworks>
Bogus.Text
.NET Core Assembly project. Multi-targeting:<TargetFrameworks>net40;netstandard1.3;netstandard2.0</TargetFrameworks>
Bogus.Premium.Tests
xUnit project referencing the projects above.Bogus.Tools.Analyzer
.NET Analyzer Project. Single-targeting:<TargetFramework>netstandard1.3</TargetFramework>
(No direct dependency on
Bogus.Healthcare
)Bogus.Tools.Analyzer.Test
.NET Analyzer MS Test Project that referencesBogus.Tools.Analyzer
(Again, no direct dependency on
Bogus.Healtchare
)Bogus.Tools.Analyzer.Vsix
Visual Studio Analyzer package project that does referenceBogus.Tools.Analyzer
.The very first project MS Build attempts to build is
Bogus.Healthcare
. I'm using F# FAKE that calls into MS Build to compile everything on a CI (TeamCity) server. TeamCity server starts the build with the following command line:But for some weird reason, I get the following error.
This build fails reliably, every time on my private CI TeamCity server. I can also sometimes get this build error on my development machine.
Thanks a bunch,
Brian
π« π₯ Chaos Chaos - Do You Feel It?
Version Info
The text was updated successfully, but these errors were encountered: