Microsoft.AspNetCore.App metapackage

aspnetcore/fundamentals/metapackage-app.md

@@ -0,0 +1,58 @@
+---
+title: Microsoft.AspNetCore.App metapackage for ASP.NET Core 2.x and later
+author: Rick-Anderson
+description: The Microsoft.AspNetCore.App metapackage includes all supported ASP.NET Core and Entity Framework Core packages, along with their dependencies.
+manager: wpickett
+monikerRange: '>= aspnetcore-2.1'
+ms.author: riande
+ms.date: 09/20/2017
+ms.prod: asp.net-core
+ms.technology: aspnet
+ms.topic: article
+uid: fundamentals/metapackage-app
+---
+
+# Microsoft.AspNetCore.App metapackage for ASP.NET Core 2.1
+
+This feature requires ASP.NET Core 2.1 and later targeting .NET Core 2.1 and later.
+
+The [Microsoft.AspNetCore.App](https://www.nuget.org/packages/Microsoft.AspNetCore.App) metapackage for ASP.NET Core includes:
+
+* All supported packages by the ASP.NET Core team.
+* All supported packages by the Entity Framework Core. 
+* Internal dependencies used by ASP.NET Core and Entity Framework Core.
+* 3rd-party dependencies used by ASP.NET Core and Entity Framework Core deemed necessary to ensure the major frameworks features function.
+
+All the features of ASP.NET Core 2.1 and later and Entity Framework Core 2.1 and later are included in the `Microsoft.AspNetCore.App` package. The default project templates targeting ASP.NET Core 2.1 and later use this package. We recommend applications targeting ASP.NET Core 2.1+ and Entity Framework Core 2.1+ use the `Microsoft.AspNetCore.App` package.
+
+The version number of the `Microsoft.AspNetCore.App` metapackage represents the ASP.NET Core version and Entity Framework Core version (aligned with the .NET Core version).
+
+Using the the `Microsoft.AspNetCore.App` metapackage provides version restrictions that protect your app:
+
+* Other packages added to your app cannot change the version of packages included in `Microsoft.AspNetCore.App`.
+* Version consistency ensures a reliable experience. `Microsoft.AspNetCore.App` was designed to prevent untested version combinations of related bits being used together in the same app.
+
+Applications that use the `Microsoft.AspNetCore.App` metapackage automatically take advantage of the .NET Core shared framework. When you use the `Microsoft.AspNetCore.App` metapackage, **no** assets from the referenced ASP.NET Core NuGet packages are deployed with the application — the .NET Core shared framework contains these assets. The assets in the shared framework are precompiled to improve application startup time. For more information, see "shared framework" in [.NET Core distribution packaging](/dotnet/core/build/distribution-packaging).
+
+Packages in the .NET Core shared framework are excluded in published application output.
+
+The following *.csproj* file references the `Microsoft.AspNetCore.App` metapackage for ASP.NET Core:
+
+```xml
+<Project Sdk="Microsoft.NET.Sdk.Web">
+
+  <PropertyGroup>
+    <TargetFramework>netcoreapp2.1</TargetFramework>
+  </PropertyGroup>
+
+  <ItemGroup>
+    <PackageReference Include="Microsoft.AspNetCore.App" />
+  </ItemGroup>
+
+</Project>
+
+```
+
+The preceding markup doesn't specify a version number for the `Microsoft.AspNetCore.App` NuGet package. The ASP.NET Core 2.1+ templates generate this markup without a version number. Not specifying a version is convent early in development when you want the latest version. Most teams will add a version number when deploying the app to ensure that development, test, and production are all using the same version. With a fixed version number, updates to the host will not cause the app to use a newer version of the NuGet package.
+
+If your application previously used `Migrating from Microsoft.AspNetCore.All`, see [Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App](xref:fundamentals/metapackage#migrate).

aspnetcore/fundamentals/metapackage.md

@@ -1,9 +1,9 @@
 ---
-title: Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.x and later
+title: Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.0
 author: Rick-Anderson
 description: The Microsoft.AspNetCore.All metapackage includes all supported ASP.NET Core and Entity Framework Core packages, along with their dependencies.
 manager: wpickett
-monikerRange: '= aspnetcore-2.0'
+monikerRange: '>= aspnetcore-2.0'
 ms.author: riande
 ms.date: 09/20/2017
 ms.prod: asp.net-core
@@ -12,7 +12,10 @@ ms.topic: article
 uid: fundamentals/metapackage
 ---
 
-# Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.x
+# Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.0
+
+> [!NOTE]
+> We recommend applications targeting ASP.NET Core 2.1 and later use the [Microsoft.AspNetCore.App](xref:fundamentals/metapackage-all) rather than this package. See [Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App](#migrate) in this article.
 
 This feature requires ASP.NET Core 2.x targeting .NET Core 2.x.
 
@@ -33,3 +36,35 @@ You can use the package trimming process to remove packages that you don't use.
 The following *.csproj* file references the `Microsoft.AspNetCore.All` metapackage for ASP.NET Core:
 
 [!code-xml[](../mvc/views/view-compilation/sample/MvcRazorCompileOnPublish2.csproj?highlight=9)]
+
+::: moniker range=">= aspnetcore-2.1"
+# Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.1 and later version range locking
+
+`Microsoft.AspNetCore.All` 2.1 and later specifies package dependency ranges. The package dependency ranges ensure that only the excact version specified for each dependency is allowed. Any other dependency that attempts to lift a version for a component beyond what is specified in the meta-package will result in a NuGet warning, which the Microsoft.NET.Sdk will elevate to an error by default. 
+
+::: moniker-end
+
+
+<a name="migrate"></a>
+## Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App
+
+The following packages are direct dependencies of `Microsoft.AspNetCore.All` but not the `Microsoft.AspNetCore.App` package. 
+
+* Microsoft.Data.Sqlite
+* Microsoft.Data.Sqlite.Core
+* Microsoft.EntityFrameworkCore.Sqlite
+* Microsoft.EntityFrameworkCore.Sqlite.Core
+* Microsoft.Extensions.Caching.Redis
+* Microsoft.AspNetCore.DataProtection.AzureStorage
+* Microsoft.Extensions.Configuration.AzureKeyVault
+* Microsoft.AspNetCore.DataProtection.AzureKeyVault
+* Microsoft.AspNetCore.Identity.Service.AzureKeyVault
+* Microsoft.AspNetCore.AzureKeyVault.HostingStartup
+* Microsoft.AspNetCore.ApplicationInsights.HostingStartup
+
+To move from `Microsoft.AspNetCore.All` to `Microsoft.AspNetCore.App`, if your app uses any APIs from the above packages, or packages brought in by those packages, add references to those packages in your project.
+
+Any dependencies of the preceding packages that otherwise aren't dependencies of `Microsoft.AspNetCore.App` are not included implicitly. For example:
+
+* `StackExchange.Redis` as a dependency of `Microsoft.Extensions.Caching.Redis`
+* `Microsoft.ApplicationInsights` as a dependency of `Microsoft.AspNetCore.ApplicationInsights.HostingStartup`