GitVersion: ArgumentNullException in node issue with beta0014

Tested the new beta0014 version and got the following error message while building a .net standard library after adding the package. It compiles with the beta0012 version tho.

1>------ Neues Erstellen gestartet: Projekt: TestProject, Konfiguration: Debug Any CPU ------ 1>[NuGet Minimal]: Restoring packages for C:\Users\li0nsar3c00l\AppData\Local\Temp\0vdgm03o.fg3\dummy... 1>MSBUILD : error MSB4166: Der untergeordnete Knoten "2" wurde vorzeitig beendet. Vorgang zum Herunterfahren wird durchgeführt. Diagnoseinformationen finden Sie in den Dateien namens "MSBuild_*.failure.txt" unter "C:\Users\li0nsar3c00l\AppData\Local\Temp\". Dieser Speicherort kann geändert werden, indem Sie die Umgebungsvariable MSBUILDDEBUGPATH auf ein anderes Verzeichnis festlegen. ========== Alles neu erstellen: 0 erfolgreich, 1 fehlerhaft, 0 übersprungen ==========

Content of the referred file:

UNHANDLED EXCEPTIONS FROM PROCESS 16456: ===================== 22.08.2018 00:23:51 System.ArgumentNullException: Der Wert darf nicht NULL sein. Parametername: value bei System.IO.BinaryWriter.Write(String value) bei Microsoft.Build.Framework.LazyFormattedBuildEventArgs.WriteToStream(BinaryWriter writer) bei Microsoft.Build.Framework.BuildMessageEventArgs.WriteToStream(BinaryWriter writer) bei Microsoft.Build.Shared.LogMessagePacketBase.WriteToStream(INodePacketTranslator translator) bei Microsoft.Build.Shared.LogMessagePacketBase.Translate(INodePacketTranslator translator) bei Microsoft.Build.BackEnd.NodeEndpointOutOfProcBase.RunReadLoop(Stream localReadPipe, Stream localWritePipe, ConcurrentQueue`1 localPacketQueue, AutoResetEvent localPacketAvailable, AutoResetEvent localTerminatePacketPump) ===================

Any ideas?

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 1
  • Comments: 20 (19 by maintainers)

Commits related to this issue

Most upvoted comments

Did another downgrade to vs2017 15.7.6. Now, all of the packages are working fine (beta14, beta15, and my netstandard PR one) and I am unable to repro the issue at all. I am not sure what is going on, but whilst things are working, I am going to be leaving my environment alone and not touching VS any further. I am still convinced it’s a problem that VS 15.8.X introduced but that’s just a gut feeling.