.NET SDK(s)

July 23, 2019 19:23

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?

Comments

3 comments

Bilal Al-Shahwany

July 23, 2019 19:28
Hi Todd,

.NET package is used in Windows Development platform, it does not support MacOS or other platforms. .NET Core is platform independent library, you can use it with the Visual Studio app for MacOS.

You only need to use one package depending on your platform.

Thanks

Bilal
0

Permalink
Todd Meinershagen

July 23, 2019 20:05
Bilal,

I don't think you understand my question.

I understand that .NET framework code can only support the Windows platform and that a .NET core component can be hosted on any platform. That has nothing to do with how you package the shared Split.io logic.

There are two options for supporting both .NET framework and .NET Core. Split.io decided not to use either way. They actually released two distinct NuGet packages. It could have been done with one NuGet package with either technique that I described - even if they wanted to have two different .dlls targeted at each framework (.NET or .NET core)

Todd
0

Permalink
Bilal Al-Shahwany

July 23, 2019 20:29
Ah thanks Todd, we are actually planning to unify the libraries to one package only, will pass your comments to PM.

Thanks again for clarifying.

Bilal
0

Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?