Andy Gerlicher 2b3ade043d Use a multi-proc aware MSBuild logger (#8371) ... Make use of the MSBuild distributed logger functionality and add a forwarding logger. When in a multi-proc build, the forwarding logger will decide which events to forward to the main node to be logged. Without this, all events are routed and a perf penalty is incurred.		2018-01-11 15:30:56 -08:00
..
dotnet-msbuild.Tests.csproj	Merge remote-tracking branch 'dotnet/release/15.5' into merges/release/15.5-to-master-20171206-080040	2017-12-07 09:55:12 -08:00
GivenDotnetBuildInvocation.cs	Use msbuild /restore instead of separate invocations where possible	2017-10-26 16:01:34 -07:00
GivenDotnetCleanInvocation.cs	Fix verbosity tests	2017-03-10 01:08:07 -08:00
GivenDotnetMSBuildBuildsProjects.cs	Use a multi-proc aware MSBuild logger (#8371)	2018-01-11 15:30:56 -08:00
GivenDotnetPackInvocation.cs	Make --no-build imply --no-restore for pack command.	2017-11-27 23:53:22 -08:00
GivenDotnetPublishInvocation.cs	Use msbuild /restore instead of separate invocations where possible	2017-10-26 16:01:34 -07:00
GivenDotnetRestoreInvocation.cs	Use msbuild /restore instead of separate invocations where possible	2017-10-26 16:01:34 -07:00
GivenDotnetStoreInvocation.cs	Update SDK to 2.0.0-alpha-20170410-1.	2017-04-10 14:24:52 -05:00
GivenDotnetVsTestForwardingApp.cs	Add missing copyright headers to all cs files	2017-03-02 21:04:03 -08:00
GivenForwardingApp.cs	Add missing copyright headers to all cs files	2017-03-02 21:04:03 -08:00
GivenMsbuildForwardingApp.cs	Manually merging some changes that git merged wrong and deleted from the 15.5 branch.	2017-10-13 09:56:08 -07:00
GivenMSBuildLogger.cs	Hashed telemetry and event name change (#7919)	2017-10-27 10:58:25 -07:00