Live-share: Loss of Intellisense and syntax highlighting in VS for guest

Created on 28 Jan 2020  路  9Comments  路  Source: MicrosoftDocs/live-share

Product and Version [VS/VSCode]:
OS Version [macOS/Windows]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:

Steps to Reproduce / Scenario:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Screenshots
If applicable, add screenshots to help explain your problem.

language services product-feedback

Most helpful comment

Ok, I'm able to repro, so should be pretty quick to clear up. We should have this resolved shortly! I'll keep you updated.

All 9 comments

Also, your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

Product and Version: Visual Studio Enterprise 2019, version 16.4.3
OS Version: Windows 10 version 1909 build 18363.592
Live Share Extension Version: 1.0.1510.0
Target Platform or Language: C#, asp.net core 3.1

The guest intellisense, auto-complete, quick actions and syntax highlighting are completely not working.

Do you know what IDE/Version the host is on?

And are you able to repro with a vanilla C# ASP.NET app?

Hi,
the host is:
IDE: Visual Studio Enterprise 2019 version 16.4.3
Live share extension: 1.0.1510.0

We've just tried with an empty vanilla ASP.NET core 3.1 and we've got the same result, you can see no highlighting and if I type no auto-completion, suggestions, go-to-definition, etc.
And we tried to swap between host and guest as well. Thank you.

image

Hi there, I've suffered with this issue myself. I'm watching a Microsoft stream on Twitch hosted by @csharpfritz. We've seen this fail on a couple of guest sessions where the guest is unable to get intellisense.

Here's a screenshot of the stream
image

Ok, I'm able to repro, so should be pretty quick to clear up. We should have this resolved shortly! I'll keep you updated.

any update?

@VALLIS-NERIA , I believe this is fixed on newer versions of VS. Are you still seeing it repro? If so, what's your setup?

Was this page helpful?
0 / 5 - 0 ratings