I first try without nodeReuse, just with /maxcpucount, and have the same problem.
I relaunch with /nodeReuse=True, I also have the exact same error.
I launch on multiple PC, and sometimes, on some old PC with not lot of cores/threads, it could compile without error. But in 95% of the cas, I have this error.
About the installation, I have a standard installation of Visual Studio 16.7.7 on multiple PCs, and same error on all that PC. MSBuild version 188.8.131.52604.
I also make a test on a PC with the latest version, VS 16.8.2, msbuild version 184.108.40.206705, and I have the same error too.
Note that something is strange for me: that the project with the .lastbuildstate where the error happens, if one of the first project build, and almost all projects are depending on that project. I do not really understand why.
I also have another error. I have a PostbuildEvent in a low level project (most of my project are depend on that project). This post event, is used to sign the dll. I regularly have error on that post build event. It seems that the sign tool cannot open the dll sign with write access.
And that post build event is present multiples times in the log ! (in /nodeReuse:False or /nodeReuse:True)
the project order is already define by the "Reference" property inside project. So the Project Build Order inside the solution (as well the Dependencies), is already ok, when I check inside the solution.
Each of my project/vcxproj, as reference to each project on which I have a dependency.
Hi @Francois , the "Project Build Order" is applied to sln file. And you could try to build sln file instead of vcxproj file.
Hi @Dylan Zhu-MSFT , I build the sln, here the command line I try:
Hi @Francois , I'm afraid that maxcpu will make build disorderly, so did you have a try "Project Build Order", which is like this in sln file:
If it doesn't work, maybe you need to report it to product team through "Help/Send Feedback/Report a problem" in visual studio.
Hi @Dylan Zhu-MSFT , I could try with the build order explicitly specify, but in my mind, it should already be handle by msbuild, while each project have a reference property, where we can specify on which other projects it depend on. And when we do it, inside the Visual Studio solution view, it display the right order.
But I will try to see, if it solves the problem.
Sign in to comment