Open podprad opened 2 years ago
It's probably realted to #3360
Seems to also affect v4.10.1.
Any chance of a patch version bump with the correctly signed package?
This issue starts precisely at 4.9.3 and continues through to current releases. The last, correctly-signed version is 4.9.2, based on my testing.
This issue starts precisely at 4.9.3 and continues through to current releases. The last, correctly-signed version is 4.9.2, based on my testing.
I believe so too,
Any change to solve this in a patch?
There is no bug fix in C# runtime > 4.9.2 so you can stick to that version until the code signing issue is fixed in the next release
Le 22 août 2022 à 09:22, Gerhard Barteling @.***> a écrit :
This issue starts precisely at 4.9.3 and continues through to current releases. The last, correctly-signed version is 4.9.2, based on my testing.
I believe so too,
Any change to solve this in a patch?
— Reply to this email directly, view it on GitHub https://github.com/antlr/antlr4/issues/3653#issuecomment-1221954460, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNQJHYJTZA6EBZQIVCN5DV2MTD3ANCNFSM5TLZRNEQ. You are receiving this because you are subscribed to this thread.
That is clear, thanks for all the awesome work you do
Just wondering if you found a cause, because I reported it already for 4.9.3? #3360
Hello,
I've upgraded Antlr4.Runtime.Standard from 4.8.0 to 4.10.0 and now my web project (that run on IIS) complains about invalid strong name signature:
I verified the signature manually by sn.exe:
Old version 4.8.0:
New version 4.10.0:
So it looks there is really something wrong with the signature.
I used the DLL included in the nuget package:
Best regards, Michael