Blazor intellisense stops working after publishing project

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:It bothers me. A fix would be nice]
Intellisense stops working in blazor project after every publish.

I have to restart visual studio for it to start working.

---

Original Comments

Feedback Bot on 19/09/2024, 11:27 AM:

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.

David Wengier [MSFT] on 02/10/2024, 02:18 PM:

Thanks for the report. We did previously have a bug in this area, #9900, which was fixed in 17.10. This bug report seems to have been made from 17.11, so you should have that fix. Can you confirm that the issue occurred after upgrading to 17.11?

If so, would you mind using the feedback system to add a recording to this issue, and record yourself publishing the project and show how IntelliSense breaks? It would be very helpful for us to track down the problem, as it could be something specific to your project that we missed in the previous fix.

Hrvoje Grabušić on 04/10/2024, 06:37 PM:

(private comment, text removed)

Hrvoje Grabušić on 04/10/2024, 06:49 PM:

(private comment, text removed)

Hrvoje Grabušić on 03/10/2024, 08:57 PM:

I am currently on Version 17.11.4 and this is still happening.

Could this be somehow caused by copilot or some extensions ?
Copilot works after publish but intelisense does not.

David Wengier [MSFT] on 04/10/2024, 01:22 PM:

It seems unlikely, but adding a recording of the issue should help us track it down.

unknown_temp on 07/10/2024, 09:35 AM:

Thanks for the recording and extra info. I can reproduce the issue, and am going to move this issue over to our GitHub repository so we can track the fix correctly.

For some potentially good news, I was able to get back to a working state by simply closing and reopening the individual .razor document, which is a lot quicker than restarting all of VS. Hopefully that helps as a viable workaround for now, until we’re able to ship a fix.