Aspnetcore: Renaming a razor component doesn't update IntelliSense

Created on 12 Feb 2020  路  8Comments  路  Source: dotnet/aspnetcore

_This issue has been moved from a ticket on Developer Community._


Renaming a razor component doesn't update IntelliSense so you have to restart Visual Studio to be able to build the project again.


Original Comments

Visual Studio Feedback System on 2/3/2020, 08:38 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.


Original Solutions

demonhunter solved on 2/3/2020, 05:55 AM, 0 votes:

Additional informations i forgot to mention: I'm using the newest VS 2019 Enterprise version and i'm inside a blazor project.

Author L affected-medium area-blazor area-razor.tooling bug severity-minor

Most helpful comment

@mkArtakMSFT this issue will be solved by LSPification but in order to solve it with the current infrastructure would be a decently large work item to undertake.

All 8 comments

@NTaylorMullen can you please look into this? Thanks!

I'm the reporter if there are any open questions. :)

I saw this problem a few times after doing this:

  • in solution explorer select razor component and press Ctrl+C
  • press Ctrl+V to paste a copy of component
  • in solution explorer rename pasted component to its desired name

@mkArtakMSFT this issue will be solved by LSPification but in order to solve it with the current infrastructure would be a decently large work item to undertake.

Thanks @NTaylorMullen.
Let's either park this in some 5.0 milestone as a tracking one, or close as a dupe, if you have one tracking LSP related umbrella issue.

Is the only workaround to restart at this point?

@dbrennan I believe closing and re-opening (or just opening if it wasn't previously opened) the document would fix the issue as well.

Thank you, that does in fact work!

Was this page helpful?
0 / 5 - 0 ratings