.NET 5

[georgdangl]

.NET 5

[GeorgDangl]

Hey @Xwilarg, thank you for your issue!

The project is already targeting netstandard2.0, so it's compatible with .NET 5. We're also using it in lots of .NET 5 projects, so everything should work😀

Is there something that's not working for you?

[Xwilarg]

Thanks for your quick reply, I was more asking that because of the huge amount of dependencies but at the end I'm not that sure it's related (in some projects I have the issues, in some others I don't)

[GeorgDangl]

I see, that looks like a lot of dependencies😀 Can you check which target your app resolves for Dangl.Calculator, is it using the netstandard2.0 or the netstandard1.1 one?

[Xwilarg]

Um.. May I ask you how I can do that?

[GeorgDangl]

Good question, I don’t know😀
It seems to import the NET Standard Library 1.6, which seems a bit strange. I think that one has all the other dependncies. You are just targeting ’net5.0’ in your app, right?
Maybe that dependency comes from the Antlr4.Runtime package.

[Xwilarg]

I tried with 2 projects that both target .NET 5 but only have of them have this issue so I'm not sure what I'm doing wrong

[GeorgDangl]

Can you share the project?

[Xwilarg]

Sure it's this one: https://github.com/Xwilarg/Camellia/

[GeorgDangl]

Looks like the calculator isn't referenced there yet😀 But otherwise the project looks fine, nothing wrong as far as I can see that would cause this issue.

[Xwilarg]

Yup I opened the issue before referencing it but if you try to add the NuGet package you'll have the issue I'm speaking about

[GeorgDangl]

Ah, that was easy to resolve then😀

The many dependencies come in transitively from the Antlr4.Runtime package. If you just install this one (without Dangl.Calculator), you see the same behavior:

The issue seems to come from how Antlr4.Runtime has configured it's dependencies:

As you can see, the only dependency compatible to net5.0 is netstandard1.1, which itself required the NETStandard.Library, thus including all the dependencies.

I don't think this is not going to cause any issues, since as far as I remember, the .NET Standard Library dependency is handled somehow different by .NET Core, it was something introduced for compatibility reasons or such.

[Xwilarg]

Okay I'll do that then
I'm also closing this issue since the issue is solved, thanks a lot for your time