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.

Sign up for GitHub

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

Jump to bottom

C# constructors - argument hints not displaying #36

Closed
egamma opened this issue Feb 15, 2016 · 8 comments
Closed

C# constructors - argument hints not displaying #36

egamma opened this issue Feb 15, 2016 · 8 comments
Assignees
@filipw
Labels
Bug Resolved-Fixed
Milestone
1.6

Comments

@egamma
Copy link
Contributor

egamma commented Feb 15, 2016

From @sinclairzx81 on February 15, 2016 12:47

Hi there,

I have noticed that code hints for C# class constructors are not displaying correctly. The issue seems specific to constructors only.

hint

It seems that vscode is pulling from generated XML metadata for the class if its available. In all other cases, it displays no argument information at all.

hint2

Many Thanks

Copied from original issue: microsoft/vscode#3024
@egamma egamma mentioned this issue Feb 15, 2016
Closed
@DustinCampbell
Copy link
Member

This is probably a bug in https://github.com/OmniSharp/omnisharp-roslyn. Will take a look over there.

@DustinCampbell DustinCampbell mentioned this issue May 5, 2016
Closed
@DustinCampbell DustinCampbell mentioned this issue May 26, 2016
Closed
@nicolasjinchereau
Copy link

Any news on this?

@DustinCampbell DustinCampbell mentioned this issue Jun 11, 2016
Closed
@sinclairzx81
Copy link

Is there any news on this?

Its been several months now, and this issue is causing much confusion among developers using vscode for C# development. It would be good to get some feedback on the progress of this bug.

Many thanks

@DustinCampbell DustinCampbell mentioned this issue Aug 15, 2016
Closed
@sinclairzx81
Copy link

Any news on this?

1 similar comment
@sinclairzx81
Copy link

Any news on this?

@DustinCampbell DustinCampbell mentioned this issue Dec 6, 2016
Closed
@filipw filipw mentioned this issue Dec 6, 2016
Merged
@DustinCampbell DustinCampbell added this to the 1.6 milestone Dec 6, 2016
@DustinCampbell
Copy link
Member

This will be fixed in the 1.6 release of the C# extension. Thanks @filipw!

@filipw
Copy link
Contributor

filipw commented Dec 7, 2016

great 👍 cc @sinclairzx81

@sinclairzx81
Copy link

This is awesome news. Great work @filipw, champion!! 👍 :)

@Mailaender Mailaender mentioned this issue Mar 26, 2021
Closed
dibarbet added a commit to dibarbet/vscode-csharp that referenced this issue Jun 8, 2023
@dibarbet
Merge pull request dotnet#36 from microsoft/merge-omnisharp-lsp-engine
6f36b50 
Merge omnisharp-vscode/feature/lsp-engine into feature/lsp_tools_host
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@filipw filipw

Labels
Bug Resolved-Fixed
Projects
None yet
Milestone
1.6
Development

No branches or pull requests
5 participants
@DustinCampbell @egamma @filipw @sinclairzx81 @nicolasjinchereau