Why are there two packages for .NET? In the world of interoperability between .NET and .NET Core, there are two options:
1. Target the .NET Standard and have one version that works for both frameworks
2. Multiple targeted versions with one NuGet package. When the install occurs, it checks which framework and delivers the proper version.
Split.io has created two different NuGet packages, so that clients have to make a decision to use one or the other. If we are trying to create an abstraction that will be released as a NuGet package, we are now forced to release a .NET and .NET core version instead of choosing one of the two options above.
Any chance of fixing this?
Please sign in to leave a comment.