dotnet-installer/test/dotnet-run.UnitTests/project.json

{
  "version": "1.0.0-*",
  "dependencies": {
    "Microsoft.NETCore.App": {
      "type": "platform",
      "version": "1.0.0-rc3-004443-00"
    },
    "System.Runtime.Serialization.Primitives": "4.1.1-rc3-24209-08",
    "dotnet": {
      "target": "project"
    },
    "Microsoft.DotNet.Tools.Tests.Utilities": {
      "target": "project"
    },
    "xunit": "2.1.0",
    "moq.netcore": "4.4.0-beta8",
    "dotnet-test-xunit": "1.0.0-rc2-192208-24"
  },
  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.4",
        "portable-net451+win8"
      ]
    }
  },
  "testRunner": "xunit"
}
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 15:24:57 +00:00			`{`
			`"version": "1.0.0-*",`
			`"dependencies": {`
			`"Microsoft.NETCore.App": {`
			`"type": "platform",`
Updating CoreSetup to rc3-004443-00. 2016-06-10 06:09:46 +00:00			`"version": "1.0.0-rc3-004443-00"`
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 15:24:57 +00:00			`},`
Updating CoreFx, CoreClr, CoreSetup to rc3-24209-08, rc3-24208-04, rc3-3004442-00 respectively 2016-06-10 01:56:21 +00:00			`"System.Runtime.Serialization.Primitives": "4.1.1-rc3-24209-08",`
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 15:24:57 +00: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-14 01:24:22 +00: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 21:53:18 +00: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 15:24:57 +00:00			`},`
			`"frameworks": {`
			`"netcoreapp1.0": {`
			`"imports": [`
			`"dotnet5.4",`
			`"portable-net451+win8"`
			`]`
			`}`
			`},`
			`"testRunner": "xunit"`
			`}`