9 references to LogMessage
Microsoft.Build (8)
BackEnd\BuildManager\BuildManager.cs (1)
699_nodeManager!.RegisterPacketHandler(NodePacketType.LogMessage, LogMessagePacket.FactoryForDeserialization, loggingService as INodePacketHandler);
BackEnd\Components\Communications\NodeProviderOutOfProcTaskHost.cs (1)
251(this as INodePacketFactory).RegisterPacketHandler(NodePacketType.LogMessage, LogMessagePacket.FactoryForDeserialization, this);
BackEnd\Components\Logging\LoggingService.cs (2)
1000if (packet.Type != NodePacketType.LogMessage) 1002ErrorUtilities.ThrowInternalError("Expected packet type \"{0}\" but instead got packet type \"{1}\".", nameof(NodePacketType.LogMessage), packet.Type.ToString());
INodePacket.cs (1)
20/// The values shared with MSBuildTaskHost are <see cref="LogMessage"/>,
Instance\TaskFactories\TaskHostTask.cs (2)
199(this as INodePacketFactory).RegisterPacketHandler(NodePacketType.LogMessage, LogMessagePacket.FactoryForDeserialization, this); 505case NodePacketType.LogMessage:
LogMessagePacketBase.cs (1)
328get { return NodePacketType.LogMessage; }
Microsoft.Build.Engine.UnitTests (1)
BackEnd\NodePackets_Tests.cs (1)
363Assert.Equal(NodePacketType.LogMessage, packet.Type);