Skip to content
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

Visual Studio 2022 #373

Open
mlopezqkd opened this issue Feb 3, 2022 · 5 comments
Open

Visual Studio 2022 #373

mlopezqkd opened this issue Feb 3, 2022 · 5 comments

Comments

@mlopezqkd
Copy link

mlopezqkd commented Feb 3, 2022

Is this supposed to work for VS 2022? I'm getting "CS0246: The type or namespace name 'Antlr4' could not be found."

I see Antlr4 (4.6.6) in Packages under Dependencies, and Antlr4.CodeGenerator (4.6.6) and Antlr4.Runtime (4.6.6) underneath Antlr4 (4.6.6).

Also, in the intermediate .cs file I see "System.out.println( ....". That's Java code.

The target framework for the project is .Net Core 3.1. I tried with .Net 5.0 and same problem.

Also, there's no syntax highlighting in the .g4 files.

@eMarkM
Copy link

eMarkM commented Feb 25, 2022

I'm just getting into this library myself. I can get it to run ok in 2022 myself. But is this still being supported? Last release in 2018?

Anyway, there is support for syntax highlighting in Visual Code. Also some nice tools for visualizing rules.
https://marketplace.visualstudio.com/items?itemName=mike-lischke.vscode-antlr4

@mlopezqkd
Copy link
Author

mlopezqkd commented Feb 25, 2022

I've used that in VS Code. Was trying to get it working in VS 2022.

Thanks for the response.

It doesn't look like it's being maintained.

@eMarkM
Copy link

eMarkM commented Feb 25, 2022

Yeah, I couldn't find anything for '22 either.

@mikeblas
Copy link

I've been able to externally use ANTLR by running the ANTLR compiler manually, then importing the generated *.CS files into my project. But there's no syntax highlighting or build integration for Visual Studio 2019 or newer, as far as I can tell.

@lextm
Copy link

lextm commented Sep 9, 2023

For possible quick migration path, you might read #381.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants