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

PR 64583 broke LSP-based XAML intellisense #65888

Closed
etvorun opened this issue Dec 8, 2022 · 0 comments · Fixed by #65898
Closed

PR 64583 broke LSP-based XAML intellisense #65888

etvorun opened this issue Dec 8, 2022 · 0 comments · Fixed by #65898
Assignees
@dibarbet
Labels
Area-IDE LSP issues related to the roslyn language server protocol implementation
Milestone
17.5 P3

Comments

@etvorun
Copy link
Contributor

etvorun commented Dec 8, 2022 •
edited
Loading

  1. Open VS.
  2. Open Tools > Options > Environment > Preview Features and check "XAML LSP-based intellisense".
  3. Create new WPF project (or any other XAML project, e.g. MAUI, WinUI, UWP).
  4. Open MainWindow.xaml.
  5. Place text caret at the end of <Grid> tag and press spacebar.
    Expected: intellisense showing grid properties
    Actual: no intellisense
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 8, 2022
@etvorun etvorun mentioned this issue Dec 8, 2022
Merged
@dibarbet dibarbet self-assigned this Dec 8, 2022
@dibarbet dibarbet added LSP issues related to the roslyn language server protocol implementation and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 8, 2022
@dibarbet dibarbet added this to the 17.5 P3 milestone Dec 8, 2022
@dibarbet dibarbet mentioned this issue Dec 9, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dibarbet dibarbet

Labels
Area-IDE LSP issues related to the roslyn language server protocol implementation
Projects
None yet
Milestone
17.5 P3
Development

Successfully merging a pull request may close this issue.

Fix XAML LSP by using a queue provider instead of subclassing dibarbet/roslyn
2 participants
@dibarbet @etvorun