netstandard 2.0 build

[JBaltika]

Hi guys,
I think it's long overdue to create a real netStandard 2.0 build without the runtime redirect hell. Its two different notions - can run on specific version and its builded specifically for particular netstandard version....

Just a thought

Sincerely Jim

[ericvergnaud]

You want to give it a try?

…

Le 1 déc. 2020 à 11:21, Jim Baltikauskas ***@***.***> a écrit : Hi guys, I think it's long overdue to create a real netStandard 2.0 build without the runtime redirect hell. Its two different notions - can run on specific version and its builded specifically for particular netstandard version.... <https://user-images.githubusercontent.com/1755340/100692703-61273f00-3359-11eb-93f0-d2838e8b661d.jpg> Just a thought Sincerely Jim — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2984>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZNQJARWQ5UTUVMYCFBWVLSSROLBANCNFSM4UINQSIQ>.

[KvanTTT]

I think it makes to upgrade the minimum version to netstandard2.0 or at least to add netstandard2.0, netstandard2.1 to TagetFramemeworks

[KvanTTT]

Also, maybe it makes sense to drop support of mono, vs2013, and especially net framework 3.5? I guess there are a small number of users but support consumes time and effort.

[KvanTTT]

@ericvergnaud what do you think about such changes? Are you approving them?

[ericvergnaud]

I work on Mac, and I'm not seeing net standard 2 in the list of of target frameworks in VS8.8.2 for the current project.
But it seems feasible to use that with new projects, see https://docs.microsoft.com/en-us/dotnet/core/tutorials/library-with-visual-studio-mac
So if someone is willing to invest the effort, I am supportive.
(users needing to stick to .Net 3.5 can stick to 4.9)

[KvanTTT]

I work on Mac, and I'm not seeing net standard 2 in the list of target frameworks in VS8.8.2 for the current project.

It's quite strange because netstandard2.0 is very mature and stable for the current time. But anyway it's possible to publish the package both as netstandard2.0 and as netstandard2.1.

users needing to stick to .Net 3.5 can stick to 4.9

It does not make sense to support net 4.9 if netstandard2.0 is supported because the latest supports all dotnet runtimes since 4.6.1, see the table.

[ericvergnaud]

I meant ANTLR 4.9

[ericvergnaud]

Seems it cannot be done via the UI:
https://www.danielcrabtree.com/blog/314/upgrading-to-net-core-and-net-standard-made-easy

[KvanTTT]

Users with net35 will be able to use the older version of ANTLR. Users with version >= net461 will be able to use any version of ANTLR.

[KvanTTT]

Seems it cannot be done via the UI:

It's not very important because it can be done via changing csproj file.