-
Notifications
You must be signed in to change notification settings - Fork 146
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# Intellisense for VSCode #386
Comments
Thanks @rongjiecomputer, I completely agree we need support for that. I have some plans to work in July for a week on getting this working natively in VsCode. The plan will be using a similar pattern to cpp did with: https://github.com/Microsoft/vscode-cpptools-api and provide a direct input from BuildXL graph to the csharp extension |
As I couldn't wait that long for a VSCode plugin, I installed VS2019 IDE and the VS plugin. I am quite sure the plugin is loaded (because VS is complaining that the plugin hurts startup performance), but it doesn't seem to have any effect (can't autocomplete BuildXL's C# code). |
Correct, we have another bug (#163) tracking the update to 2019 format. It is fine to use for now. |
Serge and I implemented the prototype for vscode and cpp in a branch in his repo: https://github.com/smera/BuildXL/tree/hackathon/vscodecpp I'll mark this item as 'help wanted' in case someone wants to do the work in OmniSharp to allow code in vscode like the vscode-cpptools-api or via something like Build Server Protocol from the Scala community. Untill then the previously linked workitem should address it by generating the csproj files and have omnisharp pick those up. |
It seems like the VSCode plugin built by
bxl -deployconfig release out\bin\release\ide\*
only does DScript language support. The official VSCode C# extension by Microsoft does not understand the files generated bybxl /vs
.The text was updated successfully, but these errors were encountered: