-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# runtime upgrade #2987
C# runtime upgrade #2987
Conversation
Not sure if you can make this work without updating the Java files for testing the C# target |
Yes, that's why I put |
e19282d
to
bc5d8fb
Compare
7cb8c6d
to
995dea6
Compare
…ove DOTNETCORE;NET40PLUS;NET45PLUS defined constants, add NETSTANDARD20
…S, NET45PLUS from code
…> Antlr4.Runtime.csproj
… under netstandard2.1
…, use PackageIcon property instead of outdated PackageIcon in Antlr4.csproj
…all-linux-csharp.sh, run-tests-csharp.sh
995dea6
to
e4b3ae9
Compare
…, remove Antlr.png
@ericvergnaud please review. |
@@ -162,21 +164,18 @@ matrix: | |||
stage: main-test | |||
- os: linux | |||
jdk: openjdk8 | |||
dist: trusty |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why remove this in the context of this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Travis does not work with dotnet if this dist is used, see this build for example https://travis-ci.org/github/antlr/antlr4/builds/751735906
Does it matter?
Can you help clarify how this change impacts the release process? |
Install
You can try to do it locally at frist. Mono and .NET Framework are not required at all for building. With netstandard2.0 it's possible to target NET Framework >= 4.6.1 (2015), NET Core >= 2.0, Mono >= 5.4 and other platforms (Xamarin, Unity, UWP). |
@KvanTTT heh, that build sequence work. Adding to the documentation. |
// You can specify all the values or you can default the Build and Revision Numbers | ||
// by using the '*' as shown below: | ||
// [assembly: AssemblyVersion("1.0.*")] | ||
[assembly: AssemblyVersion("4.9")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if all these things are still used, but I noticed that AssemblyVersion
changed from 4.9.0.0 in 4.9.0 to 0.0.0.0 in 4.9.1
Here are screenshots from [Package Explorer]
(https://github.com/NuGetPackageExplorer/NuGetPackageExplorer)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@KvanTTT and @ericvergnaud. oh no! did I miss updating version number? Can you tell me if this is catastrophic or whether we can leave things as they are until the next release?
Looks like the issue was introduced before you released, when merging this PR #2987 |
fix #2984