Java中有一个Null OutputStream吗？(Is there a Null OutputStream in Java?)

 你在这里混淆了几个概念。 只是因为一个版本稍后发布，并不意味着它有更多的功能。 .NET Core 1.0是一个LTS版本，将提供2或3年iirc的更新。 
 
 所以即使在1.1发布之后，还将有1.0的维护来修复错误或安全问题。 在软件开发中一直是这样，看看Java。 Java 1.8发布后，还有Java 1.7的更新。 
 
 .NET Core SDK包含用于恢复软件包，构建，部署和运行.NET Core应用程序的dotnet cli工具，它还包含提供框架DLL（如.NET Framework 4.x设置）的.NET Core运行时），您需要运行便携式应用程序。 
 
 .NET Core运行时/ SDK独立于CLI工具，也可以通过nuget包获得。 
 
 Visual Studio 2015/2017的.NET核心工具只是一组工具，允许Visual Studio添加对新项目类型的支持和构建管道。 
 
 用于VS的.NET Core Tools还包含SDK /运行时。 
 
 您需要在Azure上运行的内容取决于您的需求，并且Azure App Service实例上安装了哪种运行时，因为它们通常会落后于常规版本。 
 
 即，如果您创建了独立应用程序，这些应用程序使用.NET Core运行时部署，那么您只需使用任何版本，因为每个应用程序都有自己的可以并行运行的运行时。 
 
 如果要运行便携式应用程序（部署时支持.NET Core框架库），则需要在Azure App Service上安装正确的运行时间（Azure博客通常在新的运行时可用时发布）。 
 
 所有其他依赖于您的开发环境。 
 
 TL; DR：如果你 
 
 
 
 使用Visual Studio 2015：安装Visual Studio 2015工具（预览2）* 
 
 
 使用Visual Studio 2017：下载Visual Studio 2017 
 
 
 不要使用Visual Studio，但是要为.NET Core开发/安装.NET Core SDK 
 
 
 不要使用Visual Studio，而是要运行.NET Core Appl：Install .NET Core Runtime 
 
 
 要么 
 
 
 
 .NET Core Runtime（1.0.x或1.1.x）：只是运行时 
 
 
 dotnet-cli：只是构建/部署工具 
 
 
 .NET Core SDK：Runtime + dotnet-cli 
 
 
 .NET核心工具Visual Studio：运行时+ dotnet-cli + Visual Studio集成（和新项目模板） 
 
 
 cli工具和Visual Studio工具尚未完成，因此在预览中。 他们应该与VS2017和新的基于MSBuild的项目结构（从xproj迁移到csproj文件）进行RTM，但这不影响运行时/ SDK的状态。 

You are confusing a few concepts here. Just because a version is released later, it do not mean it has more features. .NET Core 1.0 ist an LTS release and will be supplied with updates for 2 or 3 years iirc.
 
So even after 1.1 gets released, there will be maintenance for 1.0 which fix bugs or security issues. This has always been the case in Software development, look at Java. When Java 1.8 got released, there were still updates for Java 1.7.
 
The .NET Core SDK contains the dotnet cli tools, used to restore the packages, build, deploy and run .NET Core applications and it also contains the .NET Core runtime, which provides the framework DLLs (like .NET Framework 4.x setup) which you need to run portable apps. 
 
The .NET Core runtime/SDK are independent of the CLI tools and can also be obtained via nuget packages. 
 
The .NET Core Tools for Visual Studio 2015/2017 are just a set of tools which allow Visual Studio add support to the new project types and build pipeline. 
 
The .NET Core Tools for VS also contain the SDK/runtime. 
 
What you need to run on Azure, depends on your needs and which kind of runtime is installed on the Azure App Service instances, as they usually lag a bit behind the regular releases. 
 
i.e. if you create self-contained applications, which get deployed with the .NET Core runtime, then you can just use any version, as each application will have its own runtime which can run side-by-side. 
 
If you want run portable applications (which ship w/o .NET Core framework libraries when deployed), then you need to have the correct runtime installed on Azure App Service (Azure blog usually posts when new runtimes become available). 
 
All other depends on your development environment. 
 
TL;DR: If you
 
 
 
use Visual Studio 2015: Install Visual Studio 2015 Tools (Preview 2) *
 
 
use Visual Studio 2017: Download Visual Studio 2017
 
 
don't use Visual Studio, but want to develop for/with .NET Core: Install .NET Core SDK
 
 
don't use Visual Studio, but want to run .NET Core Appl: Install .NET Core Runtime
 
 
or
 
 
 
.NET Core Runtime (1.0.x or 1.1.x): Just the runtime
 
 
dotnet-cli: Just build/deployment tools
 
 
.NET Core SDK: Runtime + dotnet-cli
 
 
.NET Core Tools for Visual Studio: Runtime + dotnet-cli + Visual Studio integration (and new project templates)
 
 
cli-tools and Visual Studio Tools are not finished yet, hence in preview. They should go RTM together with VS2017 and the new MSBuild based project structure (moving away from xproj to csproj files), but this do not effect the status of the runtime/SDK.