33 references to Trace
Microsoft.Build (33)
BackEnd\Client\MSBuildClient.cs (13)
172
CommunicationsUtilities.
Trace
("Executing build with command line '{0}'", descriptiveCommandLine);
210
CommunicationsUtilities.
Trace
("Failed to obtain the current build server state: {0}", ex);
211
CommunicationsUtilities.
Trace
("HResult: {0}.", ex.HResult);
369
CommunicationsUtilities.
Trace
("MSBuild client error: problem during packet handling occurred: {0}.", ex);
394
CommunicationsUtilities.
Trace
("MSBuild client warning: problem during querying console buffer width.", ex);
427
CommunicationsUtilities.
Trace
("Command packet of type '{0}' sent...", packet.Type);
462
CommunicationsUtilities.
Trace
("Failed to obtain the current build server state: {0}", ex);
463
CommunicationsUtilities.
Trace
("HResult: {0}.", ex.HResult);
477
CommunicationsUtilities.
Trace
("Server started with PID: {0}", msbuildProcess?.Id);
481
CommunicationsUtilities.
Trace
("Failed to launch the msbuild server: {0}", ex);
558
CommunicationsUtilities.
Trace
("MSBuild client error: packet pump unexpectedly shut down: {0}", packetPump.PacketPumpException);
629
CommunicationsUtilities.
Trace
("Retrying to connect to server after {0} ms", sw.ElapsedMilliseconds);
637
CommunicationsUtilities.
Trace
("Failed to connect to server: {0}", ex);
BackEnd\Client\MSBuildClientPacketPump.cs (2)
282
CommunicationsUtilities.
Trace
("Packet factory failed to receive package. Exception while deserializing packet {0}.", packetType);
311
CommunicationsUtilities.
Trace
("Exception occurred in the packet pump: {0}", ex);
BackEnd\Components\Communications\NodeLauncher.cs (1)
92
CommunicationsUtilities.
Trace
("Launching node from {0}", msbuildLocation);
BackEnd\Components\Communications\NodeProviderOutOfProcBase.cs (7)
175
CommunicationsUtilities.
Trace
("Shutting down node with pid = {0}", nodeProcess.Id);
366
CommunicationsUtilities.
Trace
("Could not connect to node with PID {0}; it has exited with unknown exit code. This can indicate a crash at startup", msbuildProcess.Id);
372
CommunicationsUtilities.
Trace
("Could not connect to node with PID {0}; it is still running. This can occur when two multiprocess builds run in parallel and the other one 'stole' this node", msbuildProcess.Id);
515
CommunicationsUtilities.
Trace
("Reading handshake from pipe {0}", pipeName);
523
CommunicationsUtilities.
Trace
("Successfully connected to pipe {0}...!", pipeName);
839
CommunicationsUtilities.
Trace
("Waiting for node with pid = {0} to exit", _process.Id);
867
CommunicationsUtilities.
Trace
("Killing node with pid = {0}", _process.Id);
BackEnd\Node\OutOfProcNode.cs (1)
485
CommunicationsUtilities.
Trace
("Failed to restore the original environment: {0}.", ex);
BackEnd\Node\OutOfProcServerNode.cs (2)
110
CommunicationsUtilities.
Trace
("Starting new server node with handshake {0}", handshake);
349
CommunicationsUtilities.
Trace
("Building with MSBuild server with command line {0}", command.CommandLine);
CommunicationsUtilities.cs (2)
492
CommunicationsUtilities.
Trace
("Handshake failed on part {0}. Probably the client is a different MSBuild build.", valueRead);
496
CommunicationsUtilities.
Trace
("Expected end of handshake signal but received {0}. Probably the host is a different MSBuild build.", valueRead);
NodeEndpointOutOfProcBase.cs (5)
376
CommunicationsUtilities.
Trace
("Waiting for connection {0} ms...", waitTimeRemaining);
453
CommunicationsUtilities.
Trace
("Client connection failed but we will wait for another connection. Exception: {0}", e.Message);
475
CommunicationsUtilities.
Trace
("Client connection failed. Exiting comm thread. {0}", e);
559
CommunicationsUtilities.
Trace
("Exception reading from server. {0}", e);
652
CommunicationsUtilities.
Trace
("Exception while serializing packets: {0}", e);