Frameworks and Targets update #1721
+130
−37
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| --- | ||
| title: Target frameworks | Microsoft Docs | ||
| description: Explains the concepts of target frameworks when writing .NET code. | ||
| keywords: .NET, .NET Core, framework, tfm | ||
| author: richlander | ||
| @@ -16,15 +16,15 @@ ms.assetid: 6ef56a2e-593d-497b-925a-1e25bb6df2e6 | ||
|
|
||
| The .NET ecosystem has a concept of *target frameworks*. Frameworks define the API that you can use to target a particular platform. For example, the .NET Framework 4.6 is a platform that you can target. Visual Studio and other IDEs and editors use frameworks to provide you with the correct set of APIs. NuGet also uses them to ensure that you produce and consume appropriate NuGet packages and underlying assets for the framework you're targeting. | ||
|
|
||
| Reference | Name | ||
| --- | --- | ||
| Product | .NET Framework 4.6.2 or .NET 4.6.2 | ||
| Framework | `.NETFramework,Version=4.6.2` or `net462` | ||
| Family | `.NETFramework` or `net` | ||
|
|
||
| ## 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. | ||
|
|
||
| Framework | Latest Version | Target Framework Moniker (TFM) | Compact Target Framework Moniker (TFM) | .NET Standard Version | Metapackage | ||
| :--------: | :--: | :--: | :--: | :--: | :--: | :--: | ||
| @@ -38,6 +38,14 @@ A framework is typically referenced by a short target framework moniker or *TFM* | ||
|
|
||
| Name | Abbreviation | TFMs/TxMs | ||
| --- | --- | --- | ||
| .NET Standard | netstandard | netstandard1.0 | ||
| | | netstandard1.1 | ||
| | | netstandard1.2 | ||
| | | netstandard1.3 | ||
| | | netstandard1.4 | ||
| | | netstandard1.5 | ||
| | | netstandard1.6 | ||
| .NET Core App | netcoreapp | netcoreapp1.0 | netcoreapp1.1 | ||
|
There was a problem hiding this comment. .netcoreapp1.1 should be in a new row |
||
| .NET Framework | net | net11 | ||
| | | net20 | ||
| | | net35 | ||
| @@ -68,14 +76,6 @@ Windows Phone | wp | wp [wp7] | ||
| | | wpa81 | ||
| Universal Windows Platform | uap | uap [uap10.0] | ||
| | | uap10.0 | ||
|
|
||
| ## Deprecated frameworks | ||
|
|
||
| @@ -114,165 +114,15 @@ win (Windows Store) | winrt | ||
|
|
||
| ## .NET Standard | ||
|
|
||
| The [.NET Standard](https://github.com/dotnet/standard) simplifies references between binary-compatible frameworks, allowing a single target framework to reference a combination of others. For background, see the [.NET Standard Library](library.md). | ||
|
|
||
| The [NuGet Tools Get Nearest Framework Tool](https://aka.ms/s2m3th) simulates the NuGet logic used for the selection of one framework from many available framework assets in a package based on the project's framework. To use the tool, enter one project framework and one or more package frameworks. Click the **Submit** button. The tool indicates if the package frameworks you list are compatible with the project framework you provide. | ||
|
There was a problem hiding this comment. This seems to link to version 3.5.0-beta2-1484 of the tool, when versions 3.5.0 and 4.0.0 are available. Shouldn't the link be changed to one of those? There was a problem hiding this comment. Yes, great catch! I'll fix it. Let's just go with |
||
|
|
||
| For NuGet 3.3 and earlier, use the `dotnet` series of monikers. For NuGet 3.4 and later, use the `netstandard` moniker syntax. | ||
|
There was a problem hiding this comment. Is information on how to use an old version of NuGet still useful? There was a problem hiding this comment. I'd remove it since the dotnet ones already show up as deprecated earlier |
||
|
|
||
| ## Portable Class Libraries | ||
|
There was a problem hiding this comment. this one is a really long list and we don't even recommend people using it anymore. I think in this case we could link to the NuGet topic (https://docs.microsoft.com/nuget/schema/target-frameworks#portable-class-libraries) |
||
|
|
||
| For information on Portable Class Libraries, see the [Portable Class Libraries](https://docs.microsoft.com/nuget/schema/target-frameworks#portable-class-libraries) section of the *Target Framework* topic in the NuGet documentation.. | ||
|
|
||
| Name | Description | .NET Standard | ||
| --- | --- | --- | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tfm -> TFM