From edccdc1f81fdff04ae5703a0666ba49437693942 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 4 May 2017 01:21:59 -0700 Subject: [PATCH 1/3] added net47 TFM --- docs/standard/frameworks.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/standard/frameworks.md b/docs/standard/frameworks.md index 4f7f59739c327..744a373cf8f58 100644 --- a/docs/standard/frameworks.md +++ b/docs/standard/frameworks.md @@ -4,7 +4,7 @@ description: Information surrounding target frameworks for .NET Core application keywords: .NET, .NET Core, framework, TFM author: richlander ms.author: mairaw -ms.date: 04/27/2017 +ms.date: 05/04/2017 ms.topic: article ms.prod: .net ms.technology: dotnet-standard @@ -55,7 +55,7 @@ The following table defines the set of frameworks that you can use, how they're | :-------------------: | :------------: | :----------------------------: | :------------------------------------: | :-------------------: | :---------: | | .NET Standard | 1.6.1 | .NETStandard,Version=1.6 | netstandard1.6 | N/A | [NETStandard.Library](https://www.nuget.org/packages/NETStandard.Library) | | .NET Core Application | 1.1.1 | .NETCoreApp,Version=1.1 | netcoreapp1.1 | 1.6 | [Microsoft.NETCore.App](https://www.nuget.org/packages/Microsoft.NETCore.App) | -| .NET Framework | 4.6.2 | .NETFramework,Version=4.6.2 | net462 | 1.5 | N/A | +| .NET Framework | 4.7 | .NETFramework,Version=4.7 | net47 | 1.5 | N/A | ## Supported frameworks @@ -83,6 +83,7 @@ A framework is typically referenced by a short target framework moniker or *TFM* | | | net46 | | | | net461 | | | | net462 | +| | | net47 | | Windows Store | netcore | netcore [netcore45] | | | | netcore45 [win, win8] | | | | netcore451 [win81] | From 075666bcf2c898b059d17deba88a24a06ab8168d Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 4 May 2017 01:36:28 -0700 Subject: [PATCH 2/3] Update frameworks.md --- docs/standard/frameworks.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/standard/frameworks.md b/docs/standard/frameworks.md index 744a373cf8f58..dc930fb9bcbf8 100644 --- a/docs/standard/frameworks.md +++ b/docs/standard/frameworks.md @@ -35,7 +35,7 @@ You can refer to a .NET platform or runtime. Both are equally valid. **Referring to a framework** -You can refer to a framework or targeting of a framework using long- or short-forms of the TFM. Both are equally valid. +You can refer to a framework or targeting of a framework using long- or short-forms of the Target Framework Moniker (TFM). Both are equally valid. * `.NETFramework,Version=4.6.2` * `net462` @@ -49,7 +49,7 @@ You can refer to a family of frameworks using long- or short-forms of the framew ## Latest framework versions -The following table defines the set of frameworks that you can use, how they're referenced, and which version of the [.NET Standard Library](library.md) they implement. These framework versions are the latest stable versions. Pre-release versions aren't shown. +The following table defines the set of frameworks that you can use, how they're referenced, and which version of the [.NET Standard](library.md) they implement. These framework versions are the latest stable versions. Pre-release versions aren't shown. | Framework | Latest Version | Target Framework Moniker (TFM) | Compact Target Framework Moniker (TFM) | .NET Standard Version | Metapackage | | :-------------------: | :------------: | :----------------------------: | :------------------------------------: | :-------------------: | :---------: | @@ -59,7 +59,7 @@ The following table defines the set of frameworks that you can use, how they're ## Supported frameworks -A framework is typically referenced by a short target framework moniker or *TFM*. In .NET Standard, this is also generalized to *TxM* to allow a single reference to multiple frameworks. The NuGet clients support the following frameworks. Equivalents are shown within brackets (`[]`). +A framework is typically referenced by a short TFM. In .NET Standard, this is also generalized to *TxM* to allow a single reference to multiple frameworks. The NuGet clients support the following frameworks. Equivalents are shown within brackets (`[]`). | Name | Abbreviation | TFMs/TxMs | | -------------------------- | ------------ | -------------------------------------------- | From a3b9398c7ee0ed3d3efc02061c993310761817f9 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Tue, 23 May 2017 01:42:10 -0700 Subject: [PATCH 3/3] added 2.0, feedback and simplification attempt --- docs/standard/frameworks.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/standard/frameworks.md b/docs/standard/frameworks.md index dc930fb9bcbf8..fbb097dd4ddb3 100644 --- a/docs/standard/frameworks.md +++ b/docs/standard/frameworks.md @@ -4,7 +4,7 @@ description: Information surrounding target frameworks for .NET Core application keywords: .NET, .NET Core, framework, TFM author: richlander ms.author: mairaw -ms.date: 05/04/2017 +ms.date: 05/23/2017 ms.topic: article ms.prod: .net ms.technology: dotnet-standard @@ -16,11 +16,11 @@ ms.assetid: 6ef56a2e-593d-497b-925a-1e25bb6df2e6 *Frameworks* define the objects, methods, and tools that you use to create apps and libraries. The .NET Framework is used to create apps and libraries primarily for execution on systems running a Windows operating system. .NET Core includes a framework that allows you to build apps and libraries that run on a variety of operating systems. -The terms *framework* and *platform* are sometimes confusing given how they're used in phrases. Making interpretation worse, the term *platform* has different meanings in different contexts. For example, you'll see ".NET Core" described as the ".NET Core framework" in the context of building apps and libraries and also described as the ".NET Core platform" in the context of where app and library code is executed. A *computing platform* describes *where and how* an application is run. Since .NET Core executes code with the [.NET Core Common Language Runtime (CoreCLR)](https://github.com/dotnet/coreclr), it's also a platform. The same is true of the .NET Framework, which has the [Common Language Runtime (CLR)](clr.md) to execute app and library code that was developed with the .NET Framework's framework objects, methods, and tools. You'll frequently see the term "cross-platform" in documentation; but when you see that term, you should think "cross-operating system and cross-architecture (x86, x64, arm)," because that's the meaning that the author usually intends to convey. +The terms *framework* and *platform* are sometimes confusing given how they're used in phrases and their context. For example, you'll see .NET Core described as a framework in the context of building apps and libraries and also described as a platform in the context of where app and library code is executed. A *computing platform* describes *where and how* an application is run. Since .NET Core executes code with the [.NET Core Common Language Runtime (CoreCLR)](https://github.com/dotnet/coreclr), it's also a platform. The same is true of the .NET Framework, which has the [Common Language Runtime (CLR)](clr.md) to execute app and library code that was developed with the .NET Framework's framework objects, methods, and tools. The objects and methods of frameworks are called Application Programming Interfaces (APIs). Framework APIs are used in [Visual Studio](https://www.visualstudio.com/), [Visual Studio for Mac](https://www.visualstudio.com/vs/visual-studio-mac/), [Visual Studio Code](https://code.visualstudio.com/), and other Integrated Development Environments (IDEs) and editors to provide you with the correct set of objects and methods for development. Frameworks are also used by [NuGet](https://www.nuget.org/) for the production and consumption of NuGet packages to ensure that you produce and use appropriate packages for the frameworks that you target in your app or library. -When you *target a framework* or target several of them, you've decided which sets of APIs and which versions of those APIs you would like to use. Frameworks are referenced in several ways: by product name, by long- or short-form framework names, and by family. +When you *target a framework* or target several of them, you've decided which sets of APIs and which versions of those APIs you'd like to use. Frameworks are referenced in several ways: by product name, by long or short-form framework names, and by family. ## Referring to frameworks @@ -42,7 +42,7 @@ You can refer to a framework or targeting of a framework using long- or short-fo **Referring to a family of frameworks** -You can refer to a family of frameworks using long- or short-forms of the framework ID. Both are equally valid. +You can refer to a family of frameworks using long or short-forms of the framework ID. Both are equally valid. * `.NETFramework` * `net` @@ -59,9 +59,9 @@ The following table defines the set of frameworks that you can use, how they're ## Supported frameworks -A framework is typically referenced by a short TFM. In .NET Standard, this is also generalized to *TxM* to allow a single reference to multiple frameworks. The NuGet clients support the following frameworks. Equivalents are shown within brackets (`[]`). +A framework is typically referenced by a short TFM. A TFM value can represent one or multiple frameworks. The following table shows the frameworks supported by the .NET Core SDK and the NuGet client. Equivalents are shown within brackets (`[]`). -| Name | Abbreviation | TFMs/TxMs | +| Name | Abbreviation | TFM | | -------------------------- | ------------ | -------------------------------------------- | | .NET Standard | netstandard | netstandard1.0 | | | | netstandard1.1 | @@ -70,8 +70,10 @@ A framework is typically referenced by a short TFM. In .NET Standard, this is al | | | netstandard1.4 | | | | netstandard1.5 | | | | netstandard1.6 | +| | | netstandard2.0 | | .NET Core | netcoreapp | netcoreapp1.0 | | | | netcoreapp1.1 | +| | | netcoreapp2.0 | | .NET Framework | net | net11 | | | | net20 | | | | net35 |