Use netstandard instead of netcoreapp

[garyng]

Since this is a library, using netstandard (I did it in my fork garyng@cbd0dec) instead of netcoreapp make much more sense, doesn't it?

This way you can avoid having multiple projects to support multiple version of .net core.

[shinji-san]

Hi @garyng

thank your for your feedback. This project covers the requests of different partners. These developers want to use this project in their solutions directly. Some of these build environments are restricted or have restrictions e.g. if someone uses .NET FX v4.5.2 , this person will have problems with a library which is built against a .NET Standard 2.0 (see garyng@cbd0dec). So I have to keep an eye on the C# language features, .NET APIs etc.

So I will try to provide solutions for .NET Core LTS versions. I orientate myself to .NET implementation support, .NET Standard versions and .NET Core release lifecycles
But, and I hope that satisfies your request, I will implement a solution for NuGet in the next weeks. And for that case it makes absolute sense to build against .NET standard 2.0 among other things.

Could I help you? Do not hesitate to contact me with any questions.

[garyng]

Thanks for the explanation! I didn’t think of that much!

From what I know, supporting netstandard2.0 would give you support for netcoreapp2.0 and above (since all of them implementnetstandard2.0) right? This would probably cut down the number of project files that need to be maintained. However, the netfx project still need to be there though.

[shinji-san]

You're welcome!

Short summary:

• .NET Standard specifies a set of APIs
• .NET Core describes a platform.

As long as this library is linked to your final .NET application (which must specify a platform), you are right. That's the reference assembly case (or classical NuGet case).
But there are corner use cases. In these cases this library must be an "runtime" assembly, otherwise you will get a System.BadImageFormatException ("..Reference assemblies should not be loaded for execution..") by the Assembly.LoadFrom function.
Imagine that the developer has to use/load this library at runtime, so the developer has the possibility with these extra project files.

[garyng]

Ohhh, understood. I’m still young and too naive.

Thanks a lot! I guess this can be closed.