-
Notifications
You must be signed in to change notification settings - Fork 10k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate Microsoft.AspNetCore.All #3418
Comments
Could you elaborate on the rationale please? EDIT: See aspnet/MetaPackages#255 (comment) |
I think the announcement sums it up pretty well. They want to reduce the number of dependencies of packages not owned or supported by the ASP.NET or .NET teams to just those deemed necessary to ensure the major frameworks features function.. Many people don't need |
Would it be possible to address NuGet/Home#2867—especially the security aspects—before this change goes into the released product? The more dependencies a project has, the more difficult it is to make sure none of them have outstanding security advisories, so not being able to use AspNetCore.All will add to end users' maintenance workloads. NPM have really raised the bar on this by implementing |
You do realize that using
The feature is being worked on; https://github.com/NuGet/Home/wiki/Deprecate-packages |
@PeteX I asked for that tool a year ago, but nothing has really happened so far. Created https://github.com/retirenet/dotnet-retire meanwhile. |
Hi, can we use means to ha a csprojet look like that: <Project Sdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>net472</TargetFramework>
<DebugType>full</DebugType>
<UserSecretsId>aspnet-TestApp-4265477E-A059-46D4-5678-E56D6G5J9DCE</UserSecretsId>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.2" />
<PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.1.1" PrivateAssets="All" />
</ItemGroup>
</Project> |
@ikourfaln No, the meta packages only work with .NET Core. You will have to add all dependencies explicitly with the .NET Framework. |
It's great news that deprecation in Nuget is being worked on! @khellang, you're right of course! What I meant was that you get fewer explicit dependencies. I trust Microsoft to make sure the dependencies of |
Earlier this year, we announced the Microsoft.AspNetCore.App metapackage (see aspnet/Announcements#287). That announcement said:
See our documentation for details on how to migrate from Microsoft.AspNetCore.All to .App.
We have begun working on ASP.NET Core 3.0, and as a part of that, we will stop producing the Microsoft.AspNetCore.All metapackage and the matching Microsoft.AspNetCore.All shared framework.
This package will still be available in ASP.NET Core 2.2 and will continue to receive servicing updates in ASP.NET Core 2.1.
The text was updated successfully, but these errors were encountered: