News for hackers. Stuff that matters.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by starik36 on Tuesday March 21, 2023 @08:20PM (#35254856)
So the bottom line is that .NET Core can't call a .NET Framework library. It must be converted to .NET Standard first. And despite deprecation (let's call it that), .NET 5, 6, 7, 8 will continue to support calling into .NET Standard libraries.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by matthewrobertso on Tuesday March 21, 2023 @08:29PM (#35254957)
I am not sure this is (still) correct - I am able to call into a .NET framework 4.8 library from .NET 7.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by int_19h on Tuesday March 21, 2023 @09:41PM (#35255601)
If it's built against .NET 4.8 but only uses the API surface subset that corresponds to .NET Standard, that works - but then it's effectively a .NET Standard library with metadata not properly reflecting that.
Re:Understanding the .NET ecosystem: The evolution of .NET i... by WorldMaker on Wednesday March 22, 2023 @03:41PM (#35266136)
Since .NET Fx 4.7 or 4.8 libraries consumed via NuGet are "assumed" .NET Standard 2.0 unless proven otherwise for maximal compatibility with old code.