savpek
commented
4 years ago Its likely that in another computer you don't have analyzers enabled, in that mode it re-analyzes every document at every change. With analyzers enabled it don't do that. Currently you can manually trigger project or solution level analysis from vscode with "Analyze current project" or "Analyze current solution" commands.
It's not perfect situation 😢 But i don't attleast know any api from roslyn that can directly to solve that issue. Visual studio etc. does it but i don't think that part is public (?). Developing engine that can traverse all affected documents based on change is pretty huge task to say atleast. That rename case is pretty trivial (calculate changed nodes from previous to current -> find references to them). But theres basically endles combination of possible modifications which must be combined with truth that that routine must also be very very fast because it must be calculated basically after any change on documents.
cc @filipw @david-driscoll any insights for visual studio that how it calculates those changes over documents in workspace?
an-dr-eas-k
gaoshan0621
Issue Description
Problems are only detected in the file I'm currently editing, if you don't change the file it won't detect problems.
https://gfycat.com/snappyhideouseland here's a video of what I mean.
https://gfycat.com/oblongmagnificentbarb here's a video of the expected behavior, it's the same code running on a different machine where the bug does not happen.
I've tried the same thing in a different computer with the same projects, and it worked as expected in the other computers.
It also happens with no extensions other than the C# one, and it also happens in every project.
Edit: Fixed by formatting windows/the whole computer and starting over from scratch. /shrug
Steps to Reproduce
Create/Import a project. Do something that breaks the code (rename a variable that's used somewhere else, remove a semi colon, anything like that).
Expected Behavior
It'd be reported as a problem, and the other classes that whatever change you made broke, would also be reported as a problem.
https://gfycat.com/oblongmagnificentbarb here's a video of the expected behavior, it's the same code running on a different machine where the bug does not happen.
Actual Behavior
It only detects, underlines and shows up on the problems tab after you change something in the file that is now broken.
Logs
OmniSharp log
C# log
Environment information
VSCode version: 1.42.1 C# Extension: 1.21.12
Dotnet Information
.NET Core SDK (reflecting any global.json): Version: 3.1.102 Commit: 573d158fea Runtime Environment: OS Name: Windows OS Version: 10.0.18362 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\3.1.102\ Host (useful for support): Version: 3.1.2 Commit: 916b5cba26 .NET Core SDKs installed: 3.1.102 [C:\Program Files\dotnet\sdk] .NET Core runtimes installed: Microsoft.AspNetCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-downloadVisual Studio Code Extensions
|Extension|Author|Version| |---|---|---| |bracket-pair-colorizer-2|CoenraadS|0.0.29| |code-settings-sync|Shan|3.4.3| |csharp|ms-vscode|1.21.12| |csharpextensions|jchannon|1.3.1| |prettier-vscode|SimonSiefke|1.1.18| |TabOut|albert|0.1.6| |unity-code-snippets|kleber-swf|1.3.0| |unity-tools|Tobiah|1.2.3| |vscode-icons|vscode-icons-team|10.0.0| |vscodeintellicode|VisualStudioExptTeam|1.2.5|;