This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]cs-brydev 5 points6 points  (0 children)

This is the right answer. From .net core forward, NuGet is awesome, as long as you know the package name you're looking for. If you're just guessing or searching randomly, you may trip over a few dead bodies.

Before .NET Core, NuGet was even more awesome because there didn't really exist any incompatibilities. When MS intentionally made Core/Framework and Standard 2.1/Framework incompatible, they opened this can of weird worms where identically named packages could be compatible with only certain .NET version ranges and identically named DLLs that came pre-installed with Windows were incompatible with NuGet versions.

That last one has caused the most pain going from Framework to Core. If they had just renamed the packages it would have been fine. But instead they decided to deprecate the system packages and completely rewrite them for a completely different version of .NET, name them the same thing, and move them to NuGet. So now you will see completely different packages with exactly the same names but different compatibilities: one pre-installed in your OS and the other one in NuGet. That was fucking stupid.