What is the draw back of meta package use in Asp.Net Core

Hi Chittaranjana,

Here complete information and let me know if any other help required

When you create ASP.NET Core 2.0 application running against .NET Core 2.0, you should use Microsoft.AspNetCore.All (for ASP.NET Core 2.1 and higher, Microsoft.AspNetCore.App is recommended) as this is the recommended approach and is useful to avoid a long list of dependencies.

When publishing, tree-shaking will be applied, this means: the build process will find out which packages inside the metapackage will be used and will strip them from the published folder to keep the size small.

Another reason to use it is the .NET Core Runtime Store. The Microsoft.AspNetCore.All package is part of the runtime store so it won't need to be published (as mentioned above) but more importantly, it is precompiled, so startup times improves too.

However

You can't use Microsoft.AspNetCore.All (or Microsoft.AspNetCore.App) when targeting .NET Framework >= 4.6.1, because it requires netcoreapp2.0 and netcoreapp2.1 respectively

You can't and shouldn't use it in Portable Class Libraries (PCL) due to the fact that it requires netcoreapp2.0 and PCLs should be targeting netstandard2.0. There are a few exceptions, for example if you depend on a (ASP.NET Core) package which only runs on .NET Core (or you require .NET Core only APIs), since PCLs targeting netcoreappx.y can't run on .NET Framework

https://stackoverflow.com/questions/46592816/pros-and-cons-of-microsoft-aspnetcore-all-

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/metapackage-app?view=aspnetcore-2.2

https://docs.microsoft.com/en-us/dotnet/core/packages

Thanks

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Siddhartha Sharma7y ago
Accepted answer
The *.All metapackage referenced third party dependencies, not managed by the .NET Core team. Since they did not want to implicitly rerference those third party dependencies, they had to come up with a new name for the metapackage, that does not include third party dependencies. This name seem to be *.App. So semantically speaking "App" is at least not "All". And that's it.
+1
Rajanikant Hawaldar7y ago
Hi Chittaranjana,

Here complete information and let me know if any other help required

When you create ASP.NET Core 2.0 application running against .NET Core 2.0, you should use Microsoft.AspNetCore.All (for ASP.NET Core 2.1 and higher, Microsoft.AspNetCore.App is recommended) as this is the recommended approach and is useful to avoid a long list of dependencies.
When publishing, tree-shaking will be applied, this means: the build process will find out which packages inside the metapackage will be used and will strip them from the published folder to keep the size small.
Another reason to use it is the .NET Core Runtime Store. The Microsoft.AspNetCore.All package is part of the runtime store so it won't need to be published (as mentioned above) but more importantly, it is precompiled, so startup times improves too.
However
You can't use Microsoft.AspNetCore.All (or Microsoft.AspNetCore.App) when targeting .NET Framework >= 4.6.1, because it requires netcoreapp2.0 and netcoreapp2.1 respectively
You can't and shouldn't use it in Portable Class Libraries (PCL) due to the fact that it requires netcoreapp2.0 and PCLs should be targeting netstandard2.0. There are a few exceptions, for example if you depend on a (ASP.NET Core) package which only runs on .NET Core (or you require .NET Core only APIs), since PCLs targeting netcoreappx.y can't run on .NET Framework

https://stackoverflow.com/questions/46592816/pros-and-cons-of-microsoft-aspnetcore-all-
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/metapackage-app?view=aspnetcore-2.2

https://docs.microsoft.com/en-us/dotnet/core/packages

Thanks

+1