3 ms·
It got a lot better in .NET Core three when they stopped using Nuget packages for the core framework works. Now building and updating apps based on just the cor
by MarkSweep 5y ago
It got a lot better in .NET Core three when they stopped using Nuget packages for the core framework works. Now building and updating apps based on just the core frameworks no longer installs and restores Nuget packages. This makes it faster, simpler, and takes less space on disk.
You probably still will have more Nuget packages in your ASP.NET Core project than a classic .NET Framework project would.
Details about the new system: https://github.com/dotnet/designs/blob/main/accepted/2019/targeting-packs-and-runtime-packs.md https://github.com/dotnet/designs/blob/main/accepted/2019/ta...
- t-writescode 5y agoI'm really glad they stopped that. Adding, I think it was Owin (part of the .net core framework), and then being required to update to a new version of the ... collections api? it's been a while, clearly, was one of my "... seriously?" moments when working with migrating to .net core last.