mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions
dotnet-installer/test/dotnet-run.UnitTests/project.json

29 lines
586 B
JSON
Raw Normal View History

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-12 10:24:57 -05:00
{
"version": "1.0.0-*",
"dependencies": {
"Microsoft.NETCore.App": {
"type": "platform",
Upgrade Corefx and coreclr references Microsoft.NetCore.App 1.0.0 => 1.0.1 Microsoft.NETCore.Runtime.CoreCLR 1.0.2 => 1.0.4 CLI Branding "Microsoft .NET Core 1.0.0 - SDK Preview" => "Microsoft .NET Core 1.0.1 - SDK 1.0.0 Preview 2-003122" List of changes - all project.jsons - dotnet new templates - and build projects files - shared-build-targets-utils\DependencyVersions.cs - CliDependencyVersions.cs
2016-08-30 09:52:35 -07:00
"version": "1.0.1"
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-12 10:24:57 -05:00
},
Updating CoreFX, CoreCLR, Roslyn, CoreSetup to stable versions.
2016-06-14 03:14:53 -05:00
"System.Runtime.Serialization.Primitives": "4.1.1",
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-12 10:24:57 -05:00
"dotnet": {
"target": "project"
},
"Microsoft.DotNet.Tools.Tests.Utilities": {
"target": "project"
},
"xunit": "2.1.0",
Use Moq framework instead of a concrete class to mock ICommandFactory in dotnet-run.UnitTests.
2016-05-13 20:24:22 -05:00
"moq.netcore": "4.4.0-beta8",
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-17 14:53:18 -07:00
"dotnet-test-xunit": "1.0.0-rc2-192208-24"
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-12 10:24:57 -05:00
},
"frameworks": {
"netcoreapp1.0": {
"imports": [
"dotnet5.4",
"portable-net451+win8"
]
}
},
"testRunner": "xunit"
}
Reference in a new issue Copy permalink