dotnet-installer

mirrors/dotnet-installer

Fork 0

Commit graph

Author	SHA1	Message	Date
Sridhar Periyasamy	5dc1a14e39	Upgrade the "dotnet-test-xunit" version to "1.0.0-rc2-192208-24" The earlier version "1.0.0-rc2-173361-36" is missing from the cli-deps feed.	2016-05-18 20:47:53 -05:00
Eric Erhardt	c84f41e749	Use Moq framework instead of a concrete class to mock ICommandFactory in dotnet-run.UnitTests.	2016-05-13 20:24:22 -05:00
Eric Erhardt	6bf59ffde6	Console.Write() doesn't show output until a newline When running an app with `dotnet run`, we are redirecting the standard out and error just to print it out to our standard out and error. However, we are batching the output until we hit a newline, which isn't ideal for console apps. To fix this, `dotnet run` no longer redirects the standard out and error. Fix #2777	2016-05-13 09:03:35 -05:00

Author

SHA1

Message

Date

Sridhar Periyasamy

5dc1a14e39

Upgrade the "dotnet-test-xunit" version to "1.0.0-rc2-192208-24"

The earlier version "1.0.0-rc2-173361-36" is missing from the cli-deps feed.

2016-05-18 20:47:53 -05:00

Eric Erhardt

c84f41e749

Use Moq framework instead of a concrete class to mock ICommandFactory in dotnet-run.UnitTests.

2016-05-13 20:24:22 -05:00

Eric Erhardt

6bf59ffde6

Console.Write() doesn't show output until a newline

When running an app with `dotnet run`, we are redirecting the standard out and error just to print it out to our standard out and error. However, we are batching the output until we hit a newline, which isn't ideal for console apps.

To fix this, `dotnet run` no longer redirects the standard out and error.

Fix #2777

2016-05-13 09:03:35 -05:00

3 commits