From 3af4a78cf1a05cf3bfc7b8e02ee7d3745847aab9 Mon Sep 17 00:00:00 2001 From: Livar Date: Mon, 17 Oct 2016 15:25:42 -0700 Subject: [PATCH] Removing the old work around for Sierra --- Documentation/developer-guide.md | 1 - 1 file changed, 1 deletion(-) diff --git a/Documentation/developer-guide.md b/Documentation/developer-guide.md index d9de96775..775a43641 100644 --- a/Documentation/developer-guide.md +++ b/Documentation/developer-guide.md @@ -73,4 +73,3 @@ The dotnet CLI considers any executable on the path named `dotnet-{commandName}` ## Things to Know - Any added commands are usually invoked through `dotnet {command}`. As a result of this, stdout and stderr are redirected through the driver (`dotnet`) and buffered by line. As a result of this, child commands should use Console.WriteLine in any cases where they expect output to be written immediately. Any uses of Console.Write should be followed by Console.WriteLine to ensure the output is written. -- CLI is currently based on .NET Core 1.0 which does not support OS X Sierra. If you are developing the CLI on Sierra then include `/p:SkipInvalidConfigurations=true` in your calls to `build.sh`, this will allow the build to progress sufficiently to validate your work on this platform.