-
Notifications
You must be signed in to change notification settings - Fork 4k
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.
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
Feature 'Semantic classification' is currently unavailable due to an internal error (StreamJsonRpc.RemoteInvocationException: Object reference not set to an instance of an object.) #63567
Comments
Just happened again (after restarting VS), this time while switching between one file and another.
|
Yup. Looks like it. Closing out. Thanks! |
Fixed with #62137 |
I suppose it's nice there's a fix expected in 17.4. In the meantime, 17.3 fell over again.
|
And again.
|
And again. And again. And again. And again. And again. And again. And again.... Looks like, as of 17.3.0, it's possible to get this rule into a respawn and fail loop. Restarting Visual Studio does not help—the rule starts null reffing again as soon as the project is loaded—but I was able to get it back to sanity by leaving the error up and finishing the small code edit I was in the middle of typing. IMO this is a dramatic response to someone having cut
|
Same error in Visual Studio - although stack trace shows a different error. Microsoft Visual Studio Community 2022 (64-bit) - Current
|
This continues to happen with 17.7.3: StreamJsonRpc.RemoteInvocationException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree') |
Version Used: Visual Studio 17.3.0 (for a about a week so far)
Steps to Reproduce: Routine C# coding. This popped while I was in the middle of splitting a for loop into two for loops (which may not be relevant at all) and seemed perhaps worth noting. While analyzers going offline due to exceptions isn't uncommon this is the first time I've had this particular analyzer fall over.
Expected Behavior: Semantic classification doesn't render itself unavailable.
Actual Behavior: VS raises yellow bar with message in the title and the stack trace below. Looked around a bit in %AppData%\Microsoft\VisualStudio and didn't see anything which looked like helpful additional information but please let me know if there's a log file I should consult.
The text was updated successfully, but these errors were encountered: