You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A significant majority of them are legacy .NET Standard 1.x artifacts and completely unnecessary.
To minimize the amount of packages they depend on, Langly projects have to:
Consistently target .NET Standard 2.0 as recommended by Microsoft: Some packages like Numbersome.Sets and Philosoft.BehavioralAttributes target earlier .NET Standard versions only, while others like Stringier.Rope and Collectathon.Arrays target earlier .NET Standard versions.
Conditionally reference compatibility packages: Some Langly projects unnecessarily reference compatibility packages that provide missing functionality for earlier frameworks, in newer frameworks:
System.Memory should be conditionally referenced only in .NET Standard 2.0 or earlier. Projects that use spans and don't target any later framework should multi-target to either .NET Standard 2.1 or .NET Core, and not reference this package there.
The System.ValueTuple package should be removed. Value tuples already exist in all frameworks Langly targets, even on .NET Standard 1.3.
You're absolutely correct. Thanks for the clarifications.
I've decided the 5.0.0 release (happens in 5 days) is going to just be .NET 6.0 for now, to simplify things for me, especially with getting all of this actually out the door. I'll work on older targets after that, and keep your suggestions in mind.
When I tried to install the
Stringier
metapackage on a .NET 6 project I was informed by Visual Studio that it's going to install all these packages:93 packages
A significant majority of them are legacy .NET Standard 1.x artifacts and completely unnecessary.
To minimize the amount of packages they depend on, Langly projects have to:
Numbersome.Sets
andPhilosoft.BehavioralAttributes
target earlier .NET Standard versions only, while others likeStringier.Rope
andCollectathon.Arrays
target earlier .NET Standard versions.System.Memory
should be conditionally referenced only in .NET Standard 2.0 or earlier. Projects that use spans and don't target any later framework should multi-target to either .NET Standard 2.1 or .NET Core, and not reference this package there.System.ValueTuple
package should be removed. Value tuples already exist in all frameworks Langly targets, even on .NET Standard 1.3.I would have made these changes myself and submit them in a PR, but cannot since Langly's development stopped being public.
The text was updated successfully, but these errors were encountered: