Ryan Nowak e8af1141cb Attempt to fix Razor CI flakiness ... We're seeing some test failures on the CI where the build has no output. Sure enough, using Process.Exited is trap. It doesn't guarantee that all of the output has been written when it's trigger. This is a different approach that shouldn't suffer from the same problem.		2018-01-16 17:18:44 -08:00
..
Assert.cs	WIP	2018-01-12 19:05:46 -08:00
BuildIntegrationTest.cs	Implment support for publish	2018-01-12 21:11:28 -08:00
FIleThumbPrint.cs	…
InitializeTestProjectAttribute.cs	Add support and tests for Pack and P2P reference	2018-01-10 18:09:05 -08:00
MSBuildIntegrationTestBase.cs	Implment support for publish	2018-01-12 21:11:28 -08:00
MSBuildProcessKind.cs	Add support for running tests using desktop msbuild	2018-01-05 12:52:01 -08:00
MSBuildProcessManager.cs	Attempt to fix Razor CI flakiness	2018-01-16 17:18:44 -08:00
MSBuildResult.cs	…
PackIntegrationTest.cs	Make Razor targets noop with no razor files	2018-01-11 13:59:25 -08:00
ProjectDirectory.cs	Add support and tests for Pack and P2P reference	2018-01-10 18:09:05 -08:00
PublishIntegrationTest.cs	Make Razor SDK support refs and views on publish	2018-01-14 11:43:01 -08:00
RazorCompileIntegrationTest.cs	Add tests for RazorCompile target	2018-01-12 21:11:28 -08:00
RazorGenerateIntegrationTest.cs	Skip flaky test on OSX	2018-01-12 21:01:12 -08:00