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

C# Intellisense for VSCode #386

Open
rongjiecomputer opened this issue May 29, 2019 · 4 comments
Open

C# Intellisense for VSCode #386

rongjiecomputer opened this issue May 29, 2019 · 4 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@rongjiecomputer
Copy link

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 by bxl /vs.

@dannyvv
Copy link
Member

dannyvv commented May 31, 2019

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

@rongjiecomputer
Copy link
Author

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).

@dannyvv
Copy link
Member

dannyvv commented Jun 4, 2019

Correct, we have another bug (#163) tracking the update to 2019 format. It is fine to use for now.

@dannyvv dannyvv added the help wanted Extra attention is needed label Jul 31, 2019
@dannyvv
Copy link
Member

dannyvv commented Jul 31, 2019

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 looked at using a similar approach using Omnisharp. But there did not yet exist a loop back mechanism back into vscode from omnisharp. The 2 days were not enough for me to set that up as another ProjectProvider, although I don't see any blockers for it.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants