3.7 KiB
title | author | description | monikerRange | ms.author | ms.date | uid |
---|---|---|---|---|---|---|
Microsoft.AspNetCore.All metapackage for ASP.NET Core 2.0 | Rick-Anderson | The Microsoft.AspNetCore.All metapackage includes all supported ASP.NET Core and Entity Framework Core packages, along with their dependencies. | >= aspnetcore-2.0 | riande | 09/20/2017 | fundamentals/metapackage |
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 rather than this package. See Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App in this article.
This feature requires ASP.NET Core 2.x targeting .NET Core 2.x.
The Microsoft.AspNetCore.All metapackage for ASP.NET Core includes:
- All supported packages by the ASP.NET Core team.
- All supported packages by the Entity Framework Core.
- Internal and 3rd-party dependencies used by ASP.NET Core and Entity Framework Core.
All the features of ASP.NET Core 2.x and Entity Framework Core 2.x are included in the Microsoft.AspNetCore.All
package. The default project templates targeting ASP.NET Core 2.0 use this package.
The version number of the Microsoft.AspNetCore.All
metapackage represents the ASP.NET Core version and Entity Framework Core version.
Applications that use the Microsoft.AspNetCore.All
metapackage automatically take advantage of the .NET Core Runtime Store. The Runtime Store contains all the runtime assets needed to run ASP.NET Core 2.x applications. When you use the Microsoft.AspNetCore.All
metapackage, no assets from the referenced ASP.NET Core NuGet packages are deployed with the application — the .NET Core Runtime Store contains these assets. The assets in the Runtime Store are precompiled to improve application startup time.
You can use the package trimming process to remove packages that you don't use. Trimmed packages are excluded in published application output.
The following .csproj file references the Microsoft.AspNetCore.All
metapackage for ASP.NET Core:
Migrating from Microsoft.AspNetCore.All to Microsoft.AspNetCore.App
The following packages are included in Microsoft.AspNetCore.All
but not the Microsoft.AspNetCore.App
package.
Microsoft.AspNetCore.ApplicationInsights.HostingStartup
Microsoft.AspNetCore.AzureAppServices.HostingStartup
Microsoft.AspNetCore.AzureAppServicesIntegration
Microsoft.AspNetCore.DataProtection.AzureKeyVault
Microsoft.AspNetCore.DataProtection.AzureStorage
Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv
Microsoft.AspNetCore.SignalR.Redis
Microsoft.Data.Sqlite
Microsoft.Data.Sqlite.Core
Microsoft.EntityFrameworkCore.Sqlite
Microsoft.EntityFrameworkCore.Sqlite.Core
Microsoft.Extensions.Caching.Redis
Microsoft.Extensions.Configuration.AzureKeyVault
Microsoft.Extensions.Logging.AzureAppServices
Microsoft.VisualStudio.Web.BrowserLink
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 ofMicrosoft.Extensions.Caching.Redis
Microsoft.ApplicationInsights
as a dependency ofMicrosoft.AspNetCore.ApplicationInsights.HostingStartup