Replies: 4 comments 2 replies
-
Look at the json files (and others) in the top directory for usage with VS Community Edition (not VSCode) and BTW: I stopped using VSCode because I couldn't get the debugger to work. But I didn't try for very long . It might be possible. |
Beta Was this translation helpful? Give feedback.
-
That’s useful but that’s not what I’m looking for. I’m looking for code autocompletion/LSP functionality, not shortcuts for compilation and debugging (I just use the command line) |
Beta Was this translation helpful? Give feedback.
-
With those scripts and VS Community Edition autocompletion/debugging was usable for me (not perfect). I was using it with nolib + cs files of zerolib. Your usage might be different or your standards might be higher. |
Beta Was this translation helpful? Give feedback.
-
I cannot use VS Community Edition, which is presumably why it works for you. I am not on Windows. |
Beta Was this translation helpful? Give feedback.
-
Using bflat in combination with the standard C# tooling for VSCode doesn't work out well. Default configuration with Microsoft's C# LSP extension doesn't allow for code completion, and while enabling Omnisharp does make some amount of intellisense work, it defaults to the installed
dotnet
libraries (and therefore provides incorrect completions, e.g. typing inConsole.
automatically insertsusing Internal;
at the top of a file, which is invalid in bflat). I attempted pointing Omnisharp to bflat's runtime but none of the configurable paths work because it expects adotnet
-like directory structure. Disabling Omnisharp altogether just breaks code autocompletion and intellisense and no amount of configuration can fix it, at least from my attempts.If you are using bflat, what is your text editor/LSP setup? I'd like to know so I can improve my own.
Beta Was this translation helpful? Give feedback.
All reactions