Skip to content

Commit 1ee9391

Browse files
BillWagnerBillWagner
authored
Merge pull request dotnet#994 from dotnet/master
Update live with current Master
2 parents 4b0645d + bf9528b commit 1ee9391

File tree

5 files changed

+2985
-14
lines changed

5 files changed

+2985
-14
lines changed

‎docs/core/docker/index.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: Docker and .NET Core
3+
description: Docker and .NET Core
4+
keywords: Docker, .NET, .NET Core
5+
author: spboyer
6+
manager: wpickett
7+
ms.date: 09/01/2016
8+
ms.topic: article
9+
ms.prod: .net-core
10+
ms.technology: .net-core-technologies
11+
ms.devlang: dotnet
12+
ms.assetid: cae32148-aef4-4e64-a7f0-88072bad4400
13+
---
14+
15+
# Docker and .NET Core
16+
17+
The following tutorials are available for learning about using Docker with .NET Core.
18+
19+
- [Building Docker Images for .NET Core Applications](building-net-docker-images.md)
20+
21+
22+
For tutorials about developing ASP.NET Core web applications, we suggest you head over to [ASP.NET Core documentation](https://docs.asp.net).

‎docs/core/porting/libraries.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -241,9 +241,9 @@ You can target .NET Core with the traditional project system in Visual Studio, b
241241

242242
If you have more advanced project system needs, this should be your choice. Note that if you wish to multitarget by generating platform-specific assemblies like with the `xproj` project system, you'll need to create a "Bait and Switch" PCL, as described in [How to Make Portable Class Libraries Work for You](https://blogs.msdn.microsoft.com/dsplaisted/2012/08/27/how-to-make-portable-class-libraries-work-for-you/).
243243

244-
## Retargeting your .NET Framework Code to .NET Framework 4.6.1
244+
## Retargeting your .NET Framework Code to .NET Framework 4.6.2
245245

246-
If your code is not targeting .NET Framework 4.6.1, it's recommended that you retarget. This ensures that you can use the latest API alternatives for cases where the .NET Standard can't support existing APIs.
246+
If your code is not targeting .NET Framework 4.6.2, it's recommended that you retarget. This ensures that you can use the latest API alternatives for cases where the .NET Standard can't support existing APIs.
247247

248248
For each of your projects in Visual Studio you wish to port, do the following:
249249

‎docs/standard/frameworks.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Frameworks
44
keywords: .NET, .NET Core
55
author: richlander
66
manager: wpickett
7-
ms.date: 06/20/2016
7+
ms.date: 09/01/2016
88
ms.topic: article
99
ms.prod: .net-core
1010
ms.technology: .net-core-technologies
@@ -14,7 +14,7 @@ ms.assetid: 6ef56a2e-593d-497b-925a-1e25bb6df2e6
1414

1515
# Frameworks
1616

17-
The .NET ecosystem has a concept of frameworks. Frameworks define the API that you can use to target a particular platform. The .NET Framework 4.6 is one of those platforms. Frameworks are used in Visual Studio and other IDEs and editors to provide you with the correct set of APIs. They are also used by NuGet, for both production and consumption of NuGet packages, to ensure that you produce and use appropriate packages (and underlying assets) for the framework you are targeting. One can think of frameworks as one of the key currencies in the .NET ecosystem. The concept is there for correctness, to help you and your customers avoid seeing [MissingMethodException](https://docs.microsoft.com/dotnet/core/api/System.MissingMethodException) and friends at runtime.
17+
The .NET ecosystem has a concept of frameworks. Frameworks define the API that you can use to target a particular platform. The .NET Framework 4.6 is one of those platforms. Frameworks are used in Visual Studio and other IDEs and editors to provide you with the correct set of APIs. They are also used by NuGet, for both production and consumption of NuGet packages, to ensure that you produce and use appropriate packages (and underlying assets) for the framework you are targeting. One can think of frameworks as one of the key currencies in the .NET ecosystem. The concept is there for correctness, to help you and your customers avoid seeing @System.MissingMethodException and friends at runtime.
1818

1919
## Framework Versions
2020

@@ -23,10 +23,11 @@ The table below defines the set of frameworks that you can use, how they are ref
2323
| Framework | Latest Version | Target Framework Moniker (TFM) | Compact Target Framework Moniker (TFM) | .NET Standard Version | Metapackage |
2424
|:--------: | :--: | :--: | :--: | :--: | :--: | :--: |
2525
| .NET Standard | 1.6 | .NETStandard,Version=1.6 | netstandard1.6 | N/A | [NETStandard.Library](https://www.nuget.org/packages/NETStandard.Library)|
26-
| .NET Core Application | 1.0 | .NETCoreApp,Version=1.0 | netcoreapp1.0 | 1.5 | [Microsoft.NETCore.App](https://www.nuget.org/packages/Microsoft.NETCore.App)|
27-
| .NET Framework | 4.6.1 | .NETFramework,Version=4.6.1 | net461 | 1.4 | N/A |
26+
| .NET Core Application | 1.0 | .NETCoreApp,Version=1.0 | netcoreapp1.0 | 1.6 | [Microsoft.NETCore.App](https://www.nuget.org/packages/Microsoft.NETCore.App)|
27+
| .NET Framework | 4.6.2 | .NETFramework,Version=4.6.2 | net462 | 1.5 | N/A |
2828

29-
Note: These framework versions are the latest stable versions. There may be pre-released versioned as well that are not described by this table.
29+
> [!NOTE]
30+
> These framework versions are the latest stable versions. There may be pre-released versions as well that are not described by this table.
3031
3132
## Writing about Frameworks
3233

0 commit comments

Comments
 (0)